All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: linux-mtd@lists.infradead.org
Subject: Q: MTD and NIC Roms...
Date: 13 Feb 2003 00:41:47 -0700	[thread overview]
Message-ID: <m34r78bpac.fsf@lnxi.com> (raw)
In-Reply-To: <1045117634.9349.19.camel@imladris.demon.co.uk>

David Woodhouse <dwmw2@infradead.org> writes:

> On Thu, 2003-02-13 at 05:45, Eric W. Biederman wrote:
> > Currently I have a patch to eepro100.c that adds an MTD map driver so
> > the onboard rom can be written.  Making code like etherboot easier to
> > flash etc. 
> > 
> > This works by default except when everything is compiled into the
> > kernel.  In the latter case the map driver fails because NIC are
> > initialized before the mtd subsystem.  This can be handled be
> > modifying the link order of the kernel in 2.4. but that is not
> > a pretty situation.
> > 
> > I am currently looking for ideas on ways to cleanly get this code
> > into the kernel, and I am looking for ideas. 
> 
> grep --after-context=15 'BIG UGLY NOTE' drivers/mtd/
> 
> Thankfully, the inter_module_register() abortion is now gone and we can
> fix it all again in 2.5 by reverting to get_module_symbol() as it was
> before.

That one is good to hear.

Eric

  reply	other threads:[~2003-02-13  7:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  5:45 Q: MTD and NIC Roms Eric W. Biederman
2003-02-13  6:14 ` Jeff Garzik
2003-02-13  6:29   ` David Woodhouse
2003-02-13  6:47     ` Jeff Garzik
2003-02-13  7:38   ` Eric W. Biederman
2003-02-14  0:33     ` yxh
2003-02-20  3:05       ` 邹应双
2003-02-13 18:34   ` Jeremy Jackson
2003-02-13  6:27 ` David Woodhouse
2003-02-13  7:41   ` Eric W. Biederman [this message]
2003-03-06 20:20 ` Jeremy Jackson
2003-04-08 11:52   ` Eric W. Biederman

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=m34r78bpac.fsf@lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=linux-mtd@lists.infradead.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.