- Added initialize code for SB16C105x to puc.c, but
It is better to add a member (*config_function)() to
struct puc_device_description and use it
- It seems SB16C1054 *rev 0x91* has different BAR layout, but not supported yet.
I know it isn't a good thing to have many copy-and-pasted contents
(set file descriptions etc) in all MD files, but it's much more annoying
to maintain a bunch of .if \n [${MACHINE}] conditionals for all ports
and maintainers rarely notice that they also have to prepare or update
MD contents in MI content file with messy ifdefs.
XXX: of course common text should be shared by mdoc macro etc.
but I doubt playing mdoc(7) is really worth...
Detect boot page on MP e500 CPUs (P2020, MPC8572, etc) and prevent use of
that page in NetBSD. This page is used to communicate with u-boot to spin
up secondary CPUs.
Probe LBC before PCI so that LBC attached devices can be configured before
probing the PCI. This gives a chance to download/setup PCI Express switches
before probing/configuring PCI.
Fix PIXIS speed entry bug/typo.
Rework SYS_CLK logic so that the SYS_CLK config option has the highest priority.
- make sure to remove abort_task in ehci_freex
- always initialize abort_task in ehci_allocx,
not in ehci_timeout just before adding the task
Also apply similar fixes to ohci and uhci.
XXX: should we also call abort_task handler before removing it from queue
if *hci_freex() is called for usbd_xfer_handle with queued abort_task?
from common/xfer with messy mdoc .if conditionals
into MD xfer files so that developers can see
what contents are missing or obsolete and should be
written or updated
- remove some useless MD description for maintainability
XXX: still a bunch of unmaintained .if \n [${MACHINE}] in common files
pipe, as required by the spec
This helps in cases where pipes are opened/closed without reconfiguring
the device in between, eg with the ugen driver.
only for UHCI/EHCI, don't have an OHCI to test
in a simpler manner. This replaces btattach, btconfig, bthcid, btdevctl
and sdpd scripts, and also should not require any configuration settings
other than "bluetooth=YES", though the full range of configurations is
still possible.
