From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: "Kumar Gala" <kumar.gala@freescale.com>
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Second Attempt: Driver model usage on embedded processors
Date: Tue, 7 Dec 2004 07:02:15 -0500 [thread overview]
Message-ID: <1102421377.6162.8.camel@jmcmullan> (raw)
In-Reply-To: <48C50EC3-480D-11D9-8A5A-000393DBC2E8@freescale.com>
On Mon, 2004-12-06 at 23:03 -0600, Kumar Gala wrote:
> The intent was that I would use the platform_data pointer to pass =
board=20
> specific information to the driver. We would have board specific code =
> which would fill in the information. The question I have is how to=20
> handle the device variant information which is really static?
I use a 'struct device_ethernet_data' in my MPC85xx platform-device
patches at http://www.evillabs.net/~gus/patches
That seems to work well, and we could move it from
include/asm-ppc/device-ethernet.h to include/linux/device-ethernet.h to
make it more arch-independant. That covers MAC addrs and phy locations.
As for PHY IRQ, that's a thornier issue. For now, I put that in the
ethernet device's resource list.
--=20
Jason McMullan <jason.mcmullan@timesys.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jason McMullan <jason.mcmullan@timesys.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-arm-kernel@lists.arm.linux.org.uk,
Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: Second Attempt: Driver model usage on embedded processors
Date: Tue, 07 Dec 2004 07:09:37 -0500 [thread overview]
Message-ID: <1102421377.6162.8.camel@jmcmullan> (raw)
In-Reply-To: <48C50EC3-480D-11D9-8A5A-000393DBC2E8@freescale.com>
On Mon, 2004-12-06 at 23:03 -0600, Kumar Gala wrote:
> The intent was that I would use the platform_data pointer to pass board
> specific information to the driver. We would have board specific code
> which would fill in the information. The question I have is how to
> handle the device variant information which is really static?
I use a 'struct device_ethernet_data' in my MPC85xx platform-device
patches at http://www.evillabs.net/~gus/patches
That seems to work well, and we could move it from
include/asm-ppc/device-ethernet.h to include/linux/device-ethernet.h to
make it more arch-independant. That covers MAC addrs and phy locations.
As for PHY IRQ, that's a thornier issue. For now, I put that in the
ethernet device's resource list.
--
Jason McMullan <jason.mcmullan@timesys.com>
next prev parent reply other threads:[~2004-12-07 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 5:03 Second Attempt: Driver model usage on embedded processors Kumar Gala
2004-12-07 5:03 ` Kumar Gala
2004-12-07 10:55 ` Erik Mouw
2004-12-07 12:02 ` McMullan, Jason [this message]
2004-12-07 12:09 ` Jason McMullan
2004-12-07 14:53 ` Dan Malek
2004-12-07 14:53 ` Dan Malek
2004-12-08 14:53 ` Sylvain Munaut
2004-12-08 14:53 ` Sylvain Munaut
2004-12-08 16:10 ` Andy Fleming
2004-12-08 16:10 ` Andy Fleming
2004-12-08 17:11 ` Dan Malek
2004-12-08 17:11 ` Dan Malek
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=1102421377.6162.8.camel@jmcmullan \
--to=jason.mcmullan@timesys.com \
--cc=kumar.gala@freescale.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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.