From: "Brett McNerney" <mcnernbm@notes.udayton.edu>
To: <linuxppc-embedded@ozlabs.org>
Subject: Custom Driver
Date: Mon, 2 Jan 2006 22:43:55 -0500 [thread overview]
Message-ID: <000101c61017$ec64d080$0202a8c0@lilmac> (raw)
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
I am need to create a driver to interface to custom hardware on a ml403
board. I am first trying to just create a ipif register bank and access the
registers from linux but am not having any luck of yet. Has anyone
successfully done this and if so explain how or supply a driver to do this
and how to build it into the kernel? I am new at this and am having great
difficutly right now.
Thanks for any help anyone can supply
Brett
[-- Attachment #2: Type: text/html, Size: 2064 bytes --]
next reply other threads:[~2006-01-03 3:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 3:43 Brett McNerney [this message]
2006-01-03 3:59 ` Custom Driver Grant Likely
2006-01-03 12:16 ` andreas_schmidt
[not found] <000c01c6101b$2332efe0$0202a8c0@lilmac>
2006-01-06 23:02 ` Grant Likely
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='000101c61017$ec64d080$0202a8c0@lilmac' \
--to=mcnernbm@notes.udayton.edu \
--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).