my own driver (sys/dev/isa/if_iy.c) looks fishy to me.
When writing network packet data, and the multicast setup stuff, shouldn't
I use the _stream_ version of said access methods? (see functions
iy_mc_setup, iystart, and iyget)
The funny thing is that it works on a little-endian (i386) machine...
Regards,
Ignatios
> When writing network packet data, and the multicast setup stuff, shouldn't
> I use the _stream_ version of said access methods? (see functions
> iy_mc_setup, iystart, and iyget)
Yes, you should.
> The funny thing is that it works on a little-endian (i386) machine...
Of course it does; the chip is Intel, and thus little-endian (no swapping
necessary).
--
-- Jason R. Thorpe <tho...@zembu.com>
I think this would be correct, yes.
>
> The funny thing is that it works on a little-endian (i386) machine...
i386 and ISA are both little endian, so the _strean_ and non _stream_ versions
are identical. You would have problems on big-endian boxes.
--
Manuel Bouyer <bou...@antioche.eu.org>
--
David/absolute
-- www.netbsd.org: A pmap for every occasion --
> Didn't Jason mention he once thought about providing a debugging
> bus_space implementation that would bounce everything on i386
> and pick up various programming errors. Would it be possible
> to catch this as well in such a hypothetical set of code? :)
That would be bus_dma, so that people could use PCs to debug
more interesting architectures (e.g. cache coherency issues).