From: Catalin Marinas <catalin.marinas@arm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Adrian Bunk <bunk@stusta.de>,
saw@saw.sw.com.sg, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC: 2.6 patch] remove drivers/net/eepro100.c
Date: Thu, 24 Nov 2005 10:30:40 +0000 [thread overview]
Message-ID: <tnxd5kqcp7z.fsf@arm.com> (raw)
In-Reply-To: <20051123222410.GN15449@flint.arm.linux.org.uk> (Russell King's message of "Wed, 23 Nov 2005 22:24:10 +0000")
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> On Wed, Nov 23, 2005 at 10:15:48PM +0000, Russell King wrote:
>> Well, I've run 2.6.15-rc2 on what I think was the ARM platform which
>> exhibited the problem, but it doesn't show up.
>
> The test was merely a "did it successfully BOOTP" because I can't
> get it to mount and run /sbin/init from the jffs2 rootfs which
> 2.5.70 was perfectly happy to earlier today. However, the
> failure point seemed to be when NFS tried to use the card.
If you you are referring to the ARM Integrator/AP platform, I tested
it earlier this year, with a 2.6.12 kernel, and the e100.c driver
seemed to be OK with an NFS-mounted root filesystem and the IP address
got via kernel DHCP. I had problems getting the eepro100.c driver to
work though, but I didn't dig any further since e100.c seemed OK.
I'll give it another try early next week with 2.6.15-rc2 and let you
know whether I see any problems.
--
Catalin
next prev parent reply other threads:[~2005-11-24 10:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 3:33 [RFC: 2.6 patch] remove drivers/net/eepro100.c Adrian Bunk
2005-11-18 9:01 ` Russell King
2005-11-18 9:08 ` David S. Miller
2005-11-18 16:12 ` Jeff Garzik
2005-11-18 16:32 ` Russell King
2005-11-19 20:34 ` Adrian Bunk
2005-11-23 22:15 ` Russell King
2005-11-23 22:24 ` Russell King
2005-11-24 10:30 ` Catalin Marinas [this message]
2005-11-23 22:39 ` David S. Miller
2005-11-23 22:53 ` Russell King
2005-11-23 23:01 ` David S. Miller
2005-11-18 17:04 ` Tim Schmielau
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 18:18 Adrian Bunk
2006-01-05 18:57 ` Jeff Garzik
2006-01-05 21:04 ` Lennert Buytenhek
2006-01-15 0:43 ` Adrian Bunk
2006-01-15 13:19 ` Vitaly Bordug
2006-01-16 0:03 ` Stephen Hemminger
2006-01-17 18:48 ` Adrian Bunk
2006-01-17 22:27 ` John Ronciak
2006-01-18 0:32 ` John W. Linville
2006-01-18 0:36 ` Jeff Garzik
2006-01-18 10:34 ` Vitaly Bordug
2006-01-16 0:08 ` Adrian Bunk
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=tnxd5kqcp7z.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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.