From: "Grant Likely" <grant.likely@secretlab.ca>
To: "John Bonesio" <john.bonesio@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Ethernet driver for Linux kernel 2.6 running on ML403
Date: Tue, 19 Sep 2006 08:16:10 -0600 [thread overview]
Message-ID: <528646bc0609190716q4a18f769g43ef2446b0844a27@mail.gmail.com> (raw)
In-Reply-To: <2FE3DBF1797A1443AAB3FA0EF6BF4EEC021EAC01@XSJ-EXCHVS1.xlnx.xilinx.com>
[edited for context]
On 9/15/06, John Bonesio <john.bonesio@xilinx.com> wrote:
> On Thursday, September 14, 2006 5:09 PM, Keith J Outwater wrote:
> > I thinking in terms of something like a 32 bit register (i.e. like a
> > processor's PVR register) that has a hard-coded magic number
> > which a driver can read and decode to determine driver compatibility.
> > That does not sound resource-intensive given the size FPGAs we are
> > talking about. Probably don't even need 32 bits.
>
> I know that on the surface it seems like a simple thing. Some of our
> parts are big, yet some are small. We are always getting pressure to
> make our IP as small as possible.
>
> Though, this may be something we can revisit again, for now this
> information just isn't going to be available.
Then its probably just a matter of whoever configures the kernel needs
to know what version of IP is being used. ie. always have the
fallback of compile time specification of IP version. Could be done
manually, or by putting the info into the dts. We probably need a
tool to generate a dts from the .mhs or xparameters.h file anyway.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2006-09-19 14:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 19:13 Ethernet driver for Linux kernel 2.6 running on ML403 John Bonesio
2006-09-19 14:16 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 17:52 John Bonesio
2006-09-14 23:08 ` Keith J Outwater
2006-09-15 0:08 ` David H. Lynch Jr.
2006-09-15 1:14 ` David H. Lynch Jr.
2006-09-14 16:40 John Bonesio
2006-09-14 17:36 ` Keith J Outwater
2006-09-14 22:02 ` T Ziomek
2006-09-14 23:16 ` David H. Lynch Jr.
2006-09-14 22:49 ` Grant Likely
2006-09-15 16:11 ` T Ziomek
2006-09-19 10:13 ` Peter Korsgaard
2006-09-19 18:06 ` Andrew
[not found] <mailman.241.1158193867.2423.linuxppc-embedded@ozlabs.org>
2006-09-14 1:40 ` Aleck Lin
2006-09-14 1:48 ` Eugene Surovegin
2006-09-14 1:52 ` Grant Likely
2006-09-14 11:18 ` David H. Lynch Jr.
2006-09-14 13:53 ` Michael Galassi
2006-09-14 14:34 ` Grant Likely
2006-09-14 15:47 ` Keith J Outwater
2006-09-14 22:57 ` Grant Likely
2006-09-19 7:48 ` Peter Korsgaard
2006-09-19 14:17 ` Grant Likely
2006-09-19 20:10 ` Grant Likely
2006-09-19 20:40 ` David H. Lynch Jr.
2006-09-19 21:27 ` Grant Likely
2006-09-24 5:42 ` David H. Lynch Jr.
2006-09-24 14:35 ` Grant Likely
2006-09-14 23:02 ` David H. Lynch Jr.
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=528646bc0609190716q4a18f769g43ef2446b0844a27@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=john.bonesio@xilinx.com \
--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 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).