From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: netdev@vger.kernel.org
Subject: [P.A. Semi] Does the ethernet interface work on your Electra, Chitra, Nemo, and Athena board?
Date: Mon, 30 Nov 2015 10:50:17 +0100 [thread overview]
Message-ID: <565C1BD9.9040404@xenosoft.de> (raw)
In-Reply-To: <565C1B55.4020207@xenosoft.de>
FYI
On 30 November 2015 at 10:48 AM, Christian Zigotzky wrote:
> Hi Denis,
>
> Thank you for your answer. Sorry because of my description.
>
> Yes, the driver probe function finds the device.
>
> With kernel 4.4-rc3:
>
> dmesg | grep -i eth0
>
> [ 2.297473] eth0: PA Semi GMAC: intf 5, hw addr 02:00:e0:0a:30:00
>
> dhclient eth0
>
> RTNETLINK answers: Cannot allocate memory
>
> With kernel 4.1.13:
>
> dmesg | grep -i eth0
>
> [ 2.328115] eth0: PA Semi GMAC: intf 5, hw addr 02:00:e0:0a:30:00
> [ 37.130466] eth0: Link is up at 100 Mbps, full duplex.
>
> Cheers,
>
> Christian
>
> On 30 November 2015 at 09:37 AM, Denis Kirjanov wrote:
>> On 11/29/15, Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
>>> Hi All,
>>>
>>> Does the ethernet interface on your Electra, Chitra, Nemo, and Athena
>>> board work with the release candidates of the kernel 4.4? Unfortunately
>>> the P.A. Semi ethernet doesn't work on our Nemo boards with the release
>>> candidates of the kernel 4.4. We have set the following entries in the
>>> kernel config:
>>>
>>> CONFIG_NET_VENDOR_PASEMI=y
>>> CONFIG_PASEMI_MAC=y
>>>
>>> Could you please test the P.A. Semi ethernet on your P.A. Semi boards?
>> It's not clear from your descriptions what is not working. Does the
>> driver probe function find a device? Does the interface show up in
>> the kernel? Can it send/receive packets?
>>
>> Also please CC netdev.
>>
>> Thanks.
>>
>>> Thanks in advance,
>>>
>>> Christian
>>> _______________________________________________
>>> Linuxppc-dev mailing list
>>> Linuxppc-dev@lists.ozlabs.org
>>> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
next parent reply other threads:[~2015-11-30 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <565AF986.9060106@xenosoft.de>
[not found] ` <CAOJe8K1911vDjMe9m_1vY6DSGpOk0TmL96Qf1whuNFXxHJesGw@mail.gmail.com>
[not found] ` <565C1B55.4020207@xenosoft.de>
2015-11-30 9:50 ` Christian Zigotzky [this message]
2015-11-30 17:08 ` [P.A. Semi] Does the ethernet interface work on your Electra, Chitra, Nemo, and Athena board? Christian Zigotzky
2015-11-30 18:12 ` Gabriel Paubert
2015-12-01 14:47 ` Christian Zigotzky
2015-12-02 4:59 ` Christian Zigotzky
2015-12-02 8:14 ` Michael Ellerman
2015-12-02 21:11 ` Christian Zigotzky
2015-12-03 12:37 ` Christian Zigotzky
2015-12-07 12:09 ` Christian Zigotzky
2015-12-07 14:12 ` Christian Zigotzky
2015-12-08 7:32 ` Denis Kirjanov
2015-12-08 23:38 ` Benjamin Herrenschmidt
2015-12-02 8:54 ` Denis Kirjanov
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=565C1BD9.9040404@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=netdev@vger.kernel.org \
/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).