On Sat, 14 Mar 2009, Mauro Carvalho Chehab wrote:
The answer is relatively easy: Some hosts only have a SDIO interface, so
no USB, no PCI, no I2C, no MPEG2-streaming interface. So, the device has
to provide a SDIO interface in order to read and write register and to
make DMAs to get the data to the host. Think of your cell-phone, or your
PDA.
Ok, so, if I understand well, the SDIO interface will be used just like we
currently use the I2C or USB bus, right?
So, we should create some glue between DVB and SDIO bus just like we have with
PCI, USB, I2C, etc.
Ideally something like (using the design we currently have with dvb-usb):
[...]
Actually, when I created dvb-usb with the help of a lot of contributors,
it served the purpose (and still serves) that there is a lot of different
USB-based DVB devices which are delivering data. Bascially every
DVB-USB-box/card-vendor is using a generic or specific
USB-device-controller which implements some kind of high-level interface
to do e.g. I2C and streaming. Those implementations, the USB protocol and
its Linux-HAL requires some overhead to implement a driver. It was useful
to create some common module and interface.
With SDIO I can't really see the same right now. First of all, SDIO should
be much simpler as USB from the HAL point of view. Correct me if I'm
wrong, but the SDIO-host controller should give "simple" DMA access to the
device?.
Another thing for me is, there isn't many SDIO DVB devices out there right
now, where Linux support is required (the latter is a pity ;) ). Also, the
major part of supported DVB devices in Linux is PC-based and for PC (as of
today) there is PCI(e) and USB working quite well, no one needs a SDIO
device.
Having an SDIO device filling in to the DVB-API is rather straight
forward, which makes me think that right now there is no need for a
dvb-sdio.ko .
Patrick.
PS: please check the date of this email, when reading it in an archive in
2 years ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
