public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Andrei Konovalov <akonovalov@ru•mvista.com>
To: "David H. Lynch Jr" <dhlii@comcast•net>
Cc: T Ziomek <ctz001@email•mot.com>,
	linuxppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: Is there some articles discussing how to change bare-board code to linux driver?
Date: Wed, 30 Nov 2005 13:04:37 +0300	[thread overview]
Message-ID: <438D7935.20706@ru.mvista.com> (raw)
In-Reply-To: <438D0878.30503@comcast.net>

David H. Lynch Jr wrote:
> Where can I find the ./drivers/net/xilinx_enet, ... etc files.
> I can not find them in the 2.6.14.2 tree

They are in the linuxppc-2.4 tree. Try
rsync -avz --delete source.mvista.com::linuxppc-2.4 <directory>

-- Andrei

> T Ziomek wrote:
> 
>>>    Where can i find them?thanks.
>>
>>
>> In addition to LDD3 (for 2.6 kernels, or the freely available LDD2 for 
>> 2.4 kernels), you might want to look at some existing Linux drivers 
>> that are
>> based on "bare metal" / "no OS" drivers.  The ones I know of are for 
>> Xilinx
>> peripherals, for example (within the Linux kernel tree),
>> - ./drivers/net/xilinx_enet
>> - ./drivers/char/xilinx_uartlite
>> - ./drivers/char/xilinx_gpio
>>
>> Tom
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2005-11-30 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051125214126.15F9E6884D@ozlabs.org>
2005-11-30  0:35 ` Is there some articles discussing how to change bare-board code to linux driver? T Ziomek
2005-11-30  2:03   ` David H. Lynch Jr
2005-11-30 10:04     ` Andrei Konovalov [this message]
2005-11-25  6:42 zengshuai
2005-11-27  1:53 ` 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=438D7935.20706@ru.mvista.com \
    --to=akonovalov@ru$(echo .)mvista.com \
    --cc=ctz001@email$(echo .)mot.com \
    --cc=dhlii@comcast$(echo .)net \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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