--f46d04426cccad7ac904d566cbc5
Content-Type: text/plain; charset=ISO-8859-1On Sun, Feb 10, 2013 at 5:58 PM, Len Ovens wrote:
>
not really. the drivers for RME devices are PCI-species independent. the
PCI bus doesn't really exist for them, which is why the same driver can
interact with the (old) cardbus version as if it is directly on the bus.
drivers see address spaces and registers, not the bus.
>
RME devices do not load "firmware". What gets loaded is really just some
configuration data for the I/O box.
--f46d04426cccad7ac904d566cbc5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Sun, Feb 10, 2013 at 5:58 PM, Len Ove=
ns <len@ovenwerks.net> wrote:
Two linux drivers to consider. The PCIe stuff in the kernel is probably
optimized for throughput to make the best use of Video cards, fast ether
net, etc. Means larger chunks of data for less overhead. Maybe higher
latency too. It shouldn't be as it is faster than PCI which handled thi=
ngs
just fine. The extra throughput should actually help for higher channel
counts. (from reading though some of the docs on netjack)<=
div>not really. the drivers for RME devices are PCI-species independent=
. the PCI bus doesn't really exist for them, which is why the same driv=
er can interact with the (old) cardbus version as if it is directly on the =
bus. drivers see address spaces and registers, not the bus.
=A0
>
Both ends of the PCIe IF have firmware.RME device=
s do not load "firmware". What gets loaded is really just some co=
nfiguration data for the I/O box.=A0
--f46d04426cccad7ac904d566cbc5--
LINUX® is a registered trademark of Linus Torvalds in the USA and other countries.
Linuxaudio.org logo copyright Thorsten Wilms © 2006.
Hosting provided by the Virginia Tech Department of Music and DISIS.