From: "Sudhakar Rajashekhara" <sudhakar.raj@ti.com>
To: "'Mike Frysinger'" <vapier.adi@gmail.com>,
"'David Brownell'" <david-b@pacbell.net>
Cc: dwmw2@infradead.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-mtd@lists.infradead.org
Subject: RE: [PATCH] m25p80: add support for a callback to platform code on successful device probe
Date: Wed, 11 Aug 2010 17:26:07 +0530 [thread overview]
Message-ID: <02b001cb394c$2e7ec9f0$8b7c5dd0$@raj@ti.com> (raw)
In-Reply-To: <AANLkTi=RqZjXojM0XD0RhYj23fY+zrunFRtFTYGd3POp@mail.gmail.com>
Hi Mike,
On Wed, Aug 11, 2010 at 00:32:00, Mike Frysinger wrote:
> On Tue, Aug 10, 2010 at 09:07, David Brownell wrote:
> >> On Tue, Aug 10, 2010 at 12:47:05, Mike Frysinger wrote:
> >> it is necessary
> >> > that you do these things from kernel space instead of
> >> standard
> >> > userspace.
> >
> > Hard to get userspace to do this stuff if
> > you're doing a network boot, and thus need
> > to have the MAC address working early.. it's
> > easy if the kernel can get the MAC address,
> > else not possible to boot. Right?
>
> no, that isnt true at all. you can easily have a small initramfs to
> handle all of your random setup. if that's too much overhead, you can
> add a late initcall to your boards file that is run after the MTD
> devices are probed and let that read the required information. all of
> this is more than documented:
> http://www.denx.de/wiki/view/DULG/EthernetDoesNotWorkInLinux
>
I looked around in the kernel and found mtd_notifier callbacks which get
called upon addition of MTD device. Inside this callback, I am checking
for the device in which I am interested and doing a mtd->read to get the
MAC address. So this patch can be dropped.
Thanks,
Sudhakar
next prev parent reply other threads:[~2010-08-11 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 6:42 [PATCH] m25p80: add support for a callback to platform code on successful device probe Sudhakar Rajashekhara
2010-08-10 7:17 ` Mike Frysinger
2010-08-10 9:26 ` Sudhakar Rajashekhara
2010-08-10 13:07 ` David Brownell
2010-08-10 13:07 ` Sudhakar Rajashekhara
2010-08-10 19:02 ` Mike Frysinger
2010-08-11 11:56 ` Sudhakar Rajashekhara [this message]
[not found] ` <-1845909207770903949@unknownmsgid>
2010-08-11 17:27 ` Mike Frysinger
2010-08-10 13:41 ` Sergei Shtylyov
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='02b001cb394c$2e7ec9f0$8b7c5dd0$@raj@ti.com' \
--to=sudhakar.raj@ti.com \
--cc=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.com \
/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).