On 03/05/2020 20:15, Michael Walle wrote:
> The AR8031/AR8033 and the AR8035 support cable diagnostics. Adding
> driver support is straightforward, so lets add it.
>
> The PHY just do one pair at a time, so we have to start the test four
> times. The cable_test_get_status() can block and therefore
On 19/09/2019 16:44, Greg Kroah-Hartman wrote:
> On Thu, Sep 19, 2019 at 04:39:28PM +0200, Matthias May wrote:
>> On 19/09/2019 16:05, Or Gerlitz wrote:
>>> Hi Greg,
>>>
>>> If this is RTFM could you please point me to the Emm
>>>
>>> AFAIR if
On 19/09/2019 16:05, Or Gerlitz wrote:
> Hi Greg,
>
> If this is RTFM could you please point me to the Emm
>
> AFAIR if a stable kernel is not listed at kernel.org than it is EOL by now.
>
> Is this correct?
>
> thanks,
>
> Or.
>
You can also look at the wikipedia page at
https://en.wikipedi
On 14/05/2019 20:49, M. Buecher wrote:
> Preamble: I'm just a network hobbyist at home, so please bear with me if
> something in this mail is "stupid" from an expert's point of view.
>
> According to the documentation [1] "IP-Aliasing" is an obsolete way to
> manage multiple IP[v4]-addresses/masks
On 06/09/17 02:47, Andrew Lunn wrote:
>> The third and last issue will be explained in a followup email.
>
> Hi DSA hackers
>
> So there is the third issue. It affects just DSA, but it possible
> affects all DSA drivers.
>
> This patchset broken broadcast with the Marvell drivers. It could
> bre
On 13/06/17 16:20, Mason wrote:
> On 13/06/2017 11:39, Matthias May wrote:
>> On 12/06/17 15:22, Mason wrote:
>>> Hello,
>>>
>>> I am using the following drivers for Ethernet connectivity.
>>> drivers/net/ethernet/aurora/nb8800.c
>>> drivers/n
On 12/06/17 15:22, Mason wrote:
> Hello,
>
> I am using the following drivers for Ethernet connectivity.
> drivers/net/ethernet/aurora/nb8800.c
> drivers/net/phy/at803x.c
>
> Pulling the cable and plugging it back works as expected.
> (I can ping both before and after.)
>
> However, if I toggle
On 23/05/17 18:33, Timur Tabi wrote:
> On 05/23/2017 11:07 AM, Andrew Lunn wrote:
I will test that to see what happens, but I believe the real problem is
that
the at803x driver is lying when it says that the link is not okay. I think
the link is okay, and that's why I'm not ge
On 13/03/17 23:58, Andrew Lunn wrote:
> On Mon, Mar 13, 2017 at 03:42:36PM -0700, Florian Fainelli wrote:
>> On 03/13/2017 03:39 PM, Andrew Lunn wrote:
>>> On Mon, Mar 13, 2017 at 03:20:43PM -0400, Vivien Didelot wrote:
The ATU ageing time value programmed in the switch is rounded up to the
>>
On 04/01/17 17:16, Andrew Lunn wrote:
>> The setup is as follows:
>> mv88e6321:
>> * ports 0+1 connected to fibre-optics transceivers at fixed 100 Mbps
>> * port 4 is CPU port
>> * custom phy driver (replacement for marvell.ko) only populated with
>> * .config_init to
>> * set fixed speed for
On 21/11/16 14:54, Krzysztof Hałasa wrote:
> miaoq...@codeaurora.org writes:
>
>>> rmmod ath9k
>>> modprobe ath9k
>>> iw dev wlan0 set type ibss
>>> iw phy phyX set antenna 2
>>
>> 2 is a bad mask. We use bitmap, the valid masks are 1, 3, 7.
>
> Thanks for your response.
>
> I have two antenna c
11 matches
Mail list logo
