From: "Nguyen Trung Thanh" <jari.nguyen@serialsystem.com.sg>
To: "'Linuxppc-Embedded '" <linuxppc-embedded@lists.linuxppc.org>
Cc: "Brad Parker" <brad@parker.boston.ma.us>
Subject: RPX-Lite: USB microcode and SPI/IIC microcode.
Date: Thu, 15 Nov 2001 12:23:14 +0800 [thread overview]
Message-ID: <004101c16d8d$3e64e320$7b80a984@serial> (raw)
In-Reply-To: 200111141233.HAA74509@p2.parker.boston.ma.us
Hi all,
Please help me!
Now, I'm using SPI/IIC microcode patch to run SPI and Ethernet
concurrently. Thus, I could not load USB microcode patch to send
SOF.
Would you give me any idea to solve this problem?
Could I load USB microcode patch before I run USB host driver,
then reload SPI/IIC microcode when I unload USB host driver?
Of course, I cannot run SPI or IIC when running USB host driver.
Do you think that this way is applicable?
Do Motorola guys have any microcode patch for all SPI/IIC and USB_SOF? If
they have, it's really realy nice.
Urgent help needed,
Thank you very much,
Jari Nguyen Trung Thanh
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-15 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 7:05 USB host controller on FADS board IGOR LURI
2001-11-14 12:33 ` Brad Parker
2001-11-15 4:23 ` Nguyen Trung Thanh [this message]
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='004101c16d8d$3e64e320$7b80a984@serial' \
--to=jari.nguyen@serialsystem.com.sg \
--cc=brad@parker.boston.ma.us \
--cc=linuxppc-embedded@lists.linuxppc.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).