Oh btw, the pins I am talking about are the pins of the dock connector.
I am affraid that testing will be loosing time : your idea could work but require more dev than some simpler idea2- I don't even have the device, I didn't test anything myself. I have stated that.
Not really ... at least I do not think so. I mean, ok USB is serial protocol, but this does not means at all that it uses RS232 protocol and that it goes through the same controller on the mother board (in fact I am sure that this is a different controler on most motherboard. The M001 is using a SoC, so it may be the same physical component, but most probably not the same pins and part of the chip.3- Serial does not need to get routed to any usb controller. If you don't know, let me inform you about what is a USB port actually is. It means Universal Serial Bus. It is a mere interface between the serial in/out of your motherboard. And by using a ftdi chip, you can directly simulate this interface.
Good state of mindThere is nothing called as the "m001 serial" but lets assume that you mean that the serial output on the dock connector is specifically sending and receiving a specific data, pre-programmed by the manufacturer. In that case, of course this method would not work. But as I said, there is no info on this that I've seen yet. I will try it and post it to the forums once I receive the m001.
In which case it is easier to directly put a Hub on the USB internal port. That was what I mean when I said that your idea requires more dev than some other simpler idea. Anyway I have not read in depth the chip spec, but if I remember well, there is only one serial port on this chip. Meaning that the internal serial is probably just an access to the same serial than in the ipod connector.4- Anyway, on one of donaldsons topics, some guys have found a directly serial port pins on the motherboard. This means that, even the tx rx on the dock connector does not work, we can still use that serial port to get an extra usb out by the method I have mentioned.
I have used similar devices on windows environment. Interresting fact : they require a driver under windows 98 ... for me it means that they require a driver everywhere, including android. If you are lucky, this driver would be included, but I have some serious doubts ... Anyway, you are perfectly right on one point : M001 is a cheap device just for fun in dev/hardware. It does not cost much, it does not bring much, but the fun is probably to try any idea on it ...5- I am not talking theoretically, I have used ftdi chips to talk through USB on lots and lots of devices that has been using serial ports to communicate before. I don't see a reason that this wouldn't work on m001.
pin 9: SVideo Chromiance (photo)pin 10: SVideo Luminance (photo)pin 12: Serial TX -- actually D- (white)pin 13: Serial RX -- actually D+ (green)pin 14 - 16: Ground
-------------------- do set configusb 1-2: new high speed USB device using ehci_hcd and address 3===>rt_ioctl_giwscan. 6(6) BSS returned, data->length = 963usb 1-2: configuration #1 chosen from 1 choicescsi0 : SCSI emulation for USB Mass Storage devicesscsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2sd 0:0:0:0: [sda] 1001472 512-byte hardware sectors: (512 MB/489 MiB)sd 0:0:0:0: [sda] Write Protect is offsd 0:0:0:0: [sda] Assuming drive cache: write throughsd 0:0:0:0: [sda] 1001472 512-byte hardware sectors: (512 MB/489 MiB)sd 0:0:0:0: [sda] Write Protect is offsd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1sd 0:0:0:0: [sda] Attached SCSI removable disksd 0:0:0:0: Attached scsi generic sg0 type 0