From: xiangfu@sharism.cc (Xiangfu Liu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Device Driver Help
Date: Tue, 12 Apr 2011 16:12:30 +0800 [thread overview]
Message-ID: <4DA4096E.4050301@sharism.cc> (raw)
In-Reply-To: <BANLkTi=qGP0JRw1_CW1xRPOHiXcxWigaNA@mail.gmail.com>
Hi
there are some drivers code:
http://projects.qi-hardware.com/index.php/p/openwrt-xburst/source/tree/master/target/linux/xburst/files-2.6.32/drivers
you can find all datasheet here:
http://downloads.qi-hardware.com/hardware/datasheets/qi_lb60/
hardware info:
http://en.qi-hardware.com/wiki/Hardware_basics
http://en.qi-hardware.com/wiki/Hardware_basics#Schematic
the qi hardware is prompt "copyleft hardware" all source code is free software,
all document is CC.
maybe you can find some info on that project.
On 04/12/2011 02:49 PM, Niamathullah sharief wrote:
> Same question from me...Please help us....
>
> On Tue, Apr 12, 2011 at 1:15 AM, Naveen Kumar <navee83@gmail.com> wrote:
>
>> Hi,
>> I am very new to device driver area and has some basic knowledge of char
>> and block device driver and linux kernel. I am little bit aware of some of
>> subsystem of kernel but I am not able to co-relate which device driver file
>> is pure software driver and more or less part of kernel subsystem to achieve
>> hardware abstraction and which driver files deals with real hardware.
>> It would be great help if someone can provide some real example with some
>> open hardware datasheet, some basic code snippet will help me a lot.
>>
>> Thanks,
>> A Kernel Newbie
--
Best Regards
Xiangfu
-- Qi RSS feed, http://en.qi-hardware.com/feed/rss20.xml --
next prev parent reply other threads:[~2011-04-12 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 19:45 Device Driver Help Naveen Kumar
2011-04-12 6:49 ` Niamathullah sharief
2011-04-12 8:12 ` Xiangfu Liu [this message]
2011-04-12 9:22 ` Gasparini Andrea
2011-04-12 13:47 ` Xiangfu Liu
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=4DA4096E.4050301@sharism.cc \
--to=xiangfu@sharism.cc \
--cc=kernelnewbies@lists.kernelnewbies.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.