From: geoff@plan9.bell-labs.com
To: 9fans@9fans.net
Subject: [9fans] changes to the ARM SoC ports
Date: Tue, 27 Apr 2010 15:05:02 -0400 [thread overview]
Message-ID: <74d8a5c1438ed79c819ae022ed4a8efd@plan9.bell-labs.com> (raw)
booting(8) has been updated; take a look if you're using an ARM port.
On the Kirkwood SoCs (Sheevaplug and Openrd-client), USB now works.
Nemo was helpful fixing this, as usual.
One of the people here is working on using the Kirkwood crypto
acceleration hardware.
The OMAP3530 port is now available in /sys/src/9/omap. It currently
runs on the IGEPv2 board. The hardware can execute VFPv3
floating-point instructions, but 5[cal] don't generate them yet, so
floating-point is currently emulated. USB isn't quite working yet.
Once it is, we should be able to use USB Ethernet and thus run on
Beagleboards. The ohci and ehci controllers are seen, but no devices
yet. There are several USB errata that need to be looked into. From
the latest omap3530 errata:
- 3.1.1.130 only one usb dma channel (rx or tx) can be active
at one time: use interrupt mode instead
- 3.1.1.144 otg soft reset doesn't work right
- 3.1.1.183 ohci and ehci controllers cannot work concurrently
- §3.1.3 usb limitations: all ports must be configured to identical speeds
(high vs full/low)
This port is being made available now primarily as a basis for GSoC
students; we expect it to improve.
Rae McLellan of Bell Labs deserves thanks for helping to decrypt what
passes for hardware documentation these days.
next reply other threads:[~2010-04-27 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 19:05 geoff [this message]
2010-04-27 23:29 ` erik quanstrom
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=74d8a5c1438ed79c819ae022ed4a8efd@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@9fans.net \
/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).