nsamysocial.blogg.se

Videopad registration code v4.0
Videopad registration code v4.0





videopad registration code v4.0

  • support for automatical loading of bt firmware (see btusb.c)įor M-Shield AES acceleration is needed updated signed bootloader X-Loader.
  • support for loading bluetooth hardware address from DT.
  • videopad registration code v4.0

    support to be instanciated from DT instead of hciattach.This would result in the protocol being available as hci_uart_proto for usage in a hci-uart driver.Ī second driver would be needed, which would be similar to drivers/bluetooth/hci_ldisc.c with the following differences: Sre thinks, that the hci protocol extension code should be put into a file similar to drivers/bluetooth/hci_ll.c, which could be called drivers/bluetooth/hci_nokia.c (hci with nokia extensions). Most code in the driver simply configures the omap serial port and duplicates code in drivers/tty/serial/omap-serial.c. There is a TODO file in that directory, which lists the code refactoring needed to get the driver out of staging.Īpart from the things listed in that TODO file, the driver also seems to reinvent the wheel concerning the uart port. The bluetooth driver is currently available in drivers/staging/nokia_h4p. There's patchĪlso for some strange reason, mmcblk? devices do not work for root filesystem. In recent mainline (cca 3.16+), it is impossible to use nfsroot over usb0 device.

    videopad registration code v4.0

    Make INSTALL_MOD_PATH=/mnt/target modules_install

  • Yellow = Work in Progress (WIP), for docs: no documentation, but kernel code available.






  • Videopad registration code v4.0