-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Sep 8, 2007, at 22:30, Izumi Tsutsui wrote:

> joerg@britannica.bec.de wrote:
>
>>> doesn't macppc have vtophys()?
>>> any driver using it won't work on sparc64.
>>
>> In dev/pci only bktr and oboe match that (with possible conditional
>> code in de(4)).
>
> - many drivers lack necessary bus_dmamap_sync(9) calls,
>   which are mostly no-op on i386 or macppc
>   (IIRC there was a report ti(4) didn't work on sparc64)
> - some drivers are not well-tested on big endian machines
>   (some VLAN code might be still problematic for example),
>   or also could have LE64BE bugs on sparc64
> - sparc64 (or some other ports) has more assertions in MD backend
>   and some drivers could have bugs which are not caught on i386
> - some drivers might have invalid I/O accesses which only
>   work in __NO_STRICT_ALIGNMENT case
>
> etc?

Even more reasons to have these drivers in sparc64's GENERIC.
Which reminds me - gem has OpenFirmware/OBP code to find the local MAC 
address, I'll fix that.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRuNdtMpnzkX8Yg2nAQJ4vgf8DbLfYshTuO/DbRb4lbi8dIraOd9IWFcV
Cm0nApc++z4sLc3B61cYs8SJIR3b2vod5G2XJ+pegQEFrqpLP9z5RqvlOepDW4ys
VTyXYY33B/BAg+SLQ5XyYvsXhE9IJ6dR+O0UlpuK54ACRJIW/N6butLVITr1c8fx
EI9DtyXUf0M3ftcAVPy2RY9rFTLXy7Mi8vWkl5TN0YLVsaW/CHEXFDaSGhs6HuJU
4FhA1X5ePsUIXjwL6RM0H3cUSXp9ABJ15LUb0YzaEpRw5+u4B5IRNDKslKm6wXzC
ygBlT+jTGGG31sBPCK9DJEeY0l2IXr0/zZbASJf5xDkQaSaJr6VJCQ==
=Qg7J
-----END PGP SIGNATURE-----