http://mail-index.netbsd.org/port-arm/2009/07/08/msg000807.html
3. I misstake sinse 2007/08/21.
:
Details:
Remove hwuart_gpioconf. PXA270 not have HWUART.
Add ohci_gpioconf. However all selectable.
Fix pSKTSEL of pcic is selectable.
Fix MMDAT<1-3> of mci is optional.
running.
Apparently it is rare for rcorder to place it after ntpd but there was
previously nothing actually preventing it.
Fixes PR 40707 by Ondrej Tuma
names in it. We therefore now depend on it.
However, this would have then created a circular dependency because named
depended on "SERVERS", and racoon was before SERVERS and required kdc,
and kdc needs the time to be right and thus depended on ntp.
Instead, have named depend on NETWORKING (so that there is a network
there), mountcritremote (so we know that named has a directory to work
from) and syslogd (so that named has some place to spew information).
I'm not sure this is perfect, but it is certainly a big improvement
over constantly failing ntpdate runs during boot.
Bluetooth devices, and bump libbluetooth minor version.
This is a reimplementation of an API largely developed by Maksim Yevmenkin
on FreeBSD to make it easier to port BlueZ/Linux programs which depend on
something similar. Alas, the BlueZ/Linux API is incompatible and unportable
as it depends on a 'device' being referenced by an int, but this will
hopefully make it easier to port software using that.
(bump libbluetooth minor version)
+ attempt to register only if we can stat() the devpath. this works
around e.g. nfs devpath, which is useless to register to etfs
XXX: the caller should decide
introduce a new and improved "etfs" interface, which can be used
to register host files accessible from rump fs namespace. This
new interface is not restriced to block devices, and neither does
it require the same pathname in host namespace and rump namespace.
Therefore, the same host file can be represented both as a char
and block device in rump namespace.
* adjust rumpblk to make the above possible
* improve rumpfs: nodes are now created properly and not implicitly
tied to the vnode lifecycle
the end of sdattach() to the end of sd_get_parms(). The code at
the bottom of sd_get_parms() was only used for optical drives or
in the case where the drive geometry couldn't be retrived for some
reason, to create a fake geometry. The case for setting up the
real geometry was handled above that code.
