netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
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: Wed, 23 Nov 2005 22:15:48 +0000	[thread overview]
Message-ID: <20051123221547.GM15449@flint.arm.linux.org.uk> (raw)
In-Reply-To: <437DFD6C.1020106@pobox.com>

On Fri, Nov 18, 2005 at 11:12:28AM -0500, Jeff Garzik wrote:
> Russell King wrote:
> >On Fri, Nov 18, 2005 at 04:33:02AM +0100, Adrian Bunk wrote:
> >
> >>This patch removes the obsolete drivers/net/eepro100.c driver.
> >>
> >>Is there any reason why it should be kept?
> >
> >
> >Tt's the only driver which works correctly on ARM CPUs.  e100 is
> >basically buggy.  This has been discussed here on lkml and more
> >recently on linux-netdev.  If anyone has any further questions
> >please read the archives of those two lists.
> 
> After reading the archives, one discovers the current status is:
> 
> 	waiting on ARM folks to test e100
> 
> Latest reference is public message-id <4371A373.6000308@pobox.com>, 
> which was CC'd to you.
> 
> There is a patch in netdev-2.6.git#e100-sbit and in Andrew's -mm tree 
> that should solve the ARM problems, and finally allow us to kill 
> eepro100.  But it's waiting for feedback...

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.  However, that's
meaningless as it has been literally _years_ (4 or more) since the
problem was reported.  It's rather unsurprising that I can't reproduce
it - I don't even know if I'm using the right processor module!

It's far too late to try swapping modules and rebuilding everything
(if I can find the code for the boot loader still.)  Also since this
platform is being returned to whence it came tomorrow, I lose the
ability to test this.

I've been struggling all day trying to get the kernel back up and
running on this hardware due to various issues with sizes of kernels
and mtd/jffs2 incompatibilities with the jffs2 filesystem in flash.

So, all in all, resolving this issue has taken far too long and it is
now far too late to do any kind of positive testing.

I leave it up to you how to proceed.  Effectively I'm now completely
out of the loop on this with no hardware to worry about.  Sorry.

Finally, please don't assign any blame for this in my direction; I
reported it and I kept bugging people about it, and in spite of my
best efforts there was very little which was forthcoming.  Obviously
that wasn't enough.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  parent reply	other threads:[~2005-11-23 22:15 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 [this message]
2005-11-23 22:24       ` Russell King
2005-11-24 10:30         ` Catalin Marinas
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=20051123221547.GM15449@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --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 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).