From: Grant Edwards <grant.b.edwards@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: net: macb: fail when there's no PHY
Date: Thu, 3 Dec 2020 21:39:31 -0000 (UTC) [thread overview]
Message-ID: <rqbluj$l72$1@ciao.gmane.io> (raw)
In-Reply-To: 20201203211702.GK2333853@lunn.ch
On 2020-12-03, Andrew Lunn <andrew@lunn.ch> wrote:
> On Thu, Dec 03, 2020 at 03:07:58PM -0000, Grant Edwards wrote:
>
>> I don't think I can justify the additional effort to devlope and
>> maintain a custom kern-space driver.
>
> Why custom? You should contribute it.
I can't imagine that it would be useful to anybody else. My attempts
to donate drivers in the past were unproductive wastes of time, so I'm
not doing that again.
>>>> Was there some other way I should have done this with a 5.4 kernel
>>>> that I was unable to discover?
>
> Ah, i missed you are using 5.4. You should probably jump to
> 5.10. There have been quite a few changes in this area in the macb
> driver.
I don't think there's any way I could justify using a kernel that
doesn't have long-term support.
[It looks like we're going to have to abandon the effort to use
5.4. The performance is so bad compared to 2.6.33.7 that our product
just plain won't work. We've already had remove features to the get
5.4 kernel down to a usable size, but we were prepared to live with
that.]
>> BTW Andrew, we're still shipping plenty of product that running
>> eCos. :)
>
> Cool. There is still a space for such an RTOS, linux has not yet taken
> over the world everywhere.
I keep thinking that one of these days something is going to happen
that will force us to switch to a different RTOS, but it hasn't
happened yet...
--
Grant
next prev parent reply other threads:[~2020-12-03 21:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 19:59 net: macb: fail when there's no PHY Grant Edwards
2017-09-21 20:05 ` Florian Fainelli
2017-09-21 20:36 ` Grant Edwards
2017-09-21 21:35 ` Brandon Streiff
2017-09-29 7:05 ` Harini Katakam
[not found] ` <CAK=1mW6Gti0QpUjirB6PfMCiQvnDjkbb56pVKkQmpCSkRU6wtA@mail.gmail.com>
2020-12-02 18:10 ` Florian Fainelli
2020-12-02 18:24 ` Grant Edwards
2020-12-02 18:35 ` Andrew Lunn
2020-12-02 19:16 ` Grant Edwards
2020-12-02 21:11 ` Andrew Lunn
2020-12-02 21:23 ` Grant Edwards
2020-12-03 2:39 ` Andrew Lunn
2020-12-03 3:03 ` Grant Edwards
2020-12-03 3:42 ` Florian Fainelli
2020-12-03 3:54 ` Grant Edwards
2020-12-03 4:07 ` Andrew Lunn
2020-12-03 15:07 ` Grant Edwards
2020-12-03 21:17 ` Andrew Lunn
2020-12-03 21:39 ` Grant Edwards [this message]
2020-12-03 21:49 ` Andrew Lunn
2020-12-03 22:20 ` Grant Edwards
2020-12-04 8:28 ` Alexander Dahl
2020-12-04 8:28 ` Alexander Dahl
2020-12-04 8:28 ` Alexander Dahl
2020-12-04 13:42 ` Grant Edwards
2020-12-04 17:36 ` Andrew Lunn
2020-12-04 17:36 ` Andrew Lunn
2020-12-04 17:36 ` Andrew Lunn
2020-12-04 16:47 ` Florian Fainelli
2020-12-05 2:52 ` Grant Edwards
2020-12-05 3:06 ` Florian Fainelli
2020-12-03 4:00 ` Andrew Lunn
2020-12-02 18:10 ` Grant Edwards
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='rqbluj$l72$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.