From: Michelle Konzack <linux4michelle@tamay-dogan.net>
To: eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] USBHID-PDU device programming...
Date: Mon, 16 Jun 2008 09:42:00 -0000 [thread overview]
Message-ID: <20080616000424.GF20946@freenet.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hello,
writing a Kernel Module for an Operating System is "easy" but
implementing the peripherial side is the Hell...
OK I have downloaded from <http://www.usb.org/> and others several 100
pages of specifications but I have not found any hints HOW to code the
periperial part...
I have an Elececronic which I2C/1-Wire based to get Ampere, Volt and
Temperature of a Device but HOW do I code the USBHID-PDU part?
I hav tried to use a MAXQ2000 CPU and a DS80C411 but it seems, since I
have the need for an usb 1.1 Port and of course the USBHID-PDU, I have
to go with a small Atmel AM91SAM7S which include an USB port and (AFAIT)
a I2C port.
Does anyone have sample code, HOW to code the USBHID stuff?
Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
+49/177/9351947 50, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-06-16 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 9:42 Michelle Konzack [this message]
2008-06-16 10:17 ` Andrew Lunn
2008-06-17 17:55 ` [ECOS] " Michelle Konzack
2008-06-16 15:35 ` [ECOS] " Frank Pagliughi
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=20080616000424.GF20946@freenet.de \
--to=linux4michelle@tamay-dogan.net \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).