From: Heiner Kallweit <hkallweit1@gmail.com>
To: Karsten Wiborg <karsten.wiborg@web.de>, Andrew Lunn <andrew@lunn.ch>
Cc: nic_swsd@realtek.com, romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: Re: r8169 not working on 5.2.0rc6 with GPD MicroPC
Date: Mon, 1 Jul 2019 20:51:27 +0200 [thread overview]
Message-ID: <d48eb3dd-be07-1422-4649-91f3461676c4@gmail.com> (raw)
In-Reply-To: <672d3b3f-e55d-e2bb-1d8c-a83d0a0c057a@web.de>
On 01.07.2019 20:15, Karsten Wiborg wrote:
> Hi Andrew, Heiner,
>
> the device is a really small notebook. So detaching mains still leaves
> the battery which is delicately built in. So can't currently remove
> power completely.
>
> Anyway can I deliver more debugging data to you guys which might add
> support for the r8169 for this device?
>
The information is sufficient now. Still, using a random MAC address
is an emergency fallback. The device is simply broken.
I contacted GPD, let's see whether they respond something.
In parallel I'll add a random MAC address as fallback to the
mainline driver.
> Regards,
> Karsten
>
Heiner
> On 01/07/2019 15:35, Andrew Lunn wrote:
>>> When the vendor driver assigns a random MAC address, it writes it to the
>>> chip. The related registers may be persistent (can't say exactly due to
>>> missing documentation).
>>
>> If the device supports WOL, it could be it is powered using the
>> standby supply, not the main supply. Try pulling the plug from the
>> wall to really remove all power.
>>
>> Andrew
>>
>
next prev parent reply other threads:[~2019-07-01 18:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 20:34 r8169 not working on 5.2.0rc6 with GPD MicroPC Karsten Wiborg
2019-06-29 21:19 ` Karsten Wiborg
2019-06-29 22:09 ` Heiner Kallweit
2019-06-30 0:14 ` Karsten Wiborg
2019-06-30 9:12 ` Heiner Kallweit
2019-06-30 12:40 ` Karsten Wiborg
2019-06-30 14:55 ` Andrew Lunn
2019-06-30 16:03 ` Karsten Wiborg
2019-06-30 17:42 ` Heiner Kallweit
2019-06-30 21:29 ` Karsten Wiborg
2019-06-30 21:55 ` Heiner Kallweit
2019-06-30 22:21 ` Karsten Wiborg
2019-07-01 5:50 ` Heiner Kallweit
2019-07-01 13:35 ` Andrew Lunn
2019-07-01 18:15 ` Karsten Wiborg
2019-07-01 18:51 ` Heiner Kallweit [this message]
2019-07-01 19:07 ` Karsten Wiborg
2019-06-30 17:56 ` Andrew Lunn
2019-06-30 21:44 ` Karsten Wiborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d48eb3dd-be07-1422-4649-91f3461676c4@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=karsten.wiborg@web.de \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).