linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Clements <clem@clem.clem-digital.net>
To: linux-kernel@vger.kernel.org (linux-kernel)
Subject: 2.6.0-test1 and second 3c509
Date: Tue, 15 Jul 2003 11:13:27 -0400 (EDT)	[thread overview]
Message-ID: <200307151513.LAA09981@clem.clem-digital.net> (raw)


Just a reminder, I'm still backing out the 2.5.71 3c509 changes to get
my second 3c509 card. Glad to test.

Quoting viro@parcelfarce.linux.theplanet.co.uk
  > On Sun, Jun 15, 2003 at 09:52:01AM -0700, David S. Miller wrote:
  > >    From: Pete Clements <clem@clem.clem-digital.net>
  > >    Date: Sun, 15 Jun 2003 12:50:25 -0400 (EDT)
  > > 
  > >    >From boot log:
  > >    
  > >    Kernel command line: auto BOOT_IMAGE=Linux ro root=341 ether=9,0x310,4,0x3c509,eth1
  > > 
  > > Yes, that explains why the second card isn't found.
  > > 
  > > The problem is:
  > > 
  > > 1) the we can't assign a name to the device
  > >    until we've registered it with the networking
  > > 
  > > 2) without a name the boot argument lookup doesn't work
  > > 
  > > 3) we have to register the device with the networking only
  > >    after it is initialized
  > > 
  > > Hmmm...
  > 
  > Crap.  AFAICS, the clean solution would be to pass these guys (blah_probe())
  > expected device name.  And let them do allocation, etc., themselves.
  > 
  > Looking into it...
  > 

-- 
Pete Clements 


             reply	other threads:[~2003-07-15 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 15:13 Pete Clements [this message]
2003-07-16  2:06 ` 2.6.0-test1 and second 3c509 David S. Miller

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=200307151513.LAA09981@clem.clem-digital.net \
    --to=clem@clem.clem-digital.net \
    --cc=linux-kernel@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).