Vladimir 'φ-coder/phcoder' Serbinenko, le Thu 15 Mar 2012 12:30:06 +0100, a écrit : > Hello, all. I've managed to make baum driver (chosen because of qemu > support) compile in GRUB.
Yay!! > I see the functions: > static int > brl_construct (BrailleDisplay *brl, char **parameters, const char *device); >... > However they all are static. Am I supposed to use some linker magic to pick > them up? See Programs/brl_driver.h, which is included in all drivers. It's the resulting brl_driver_bm structure which is exported. > brl_writeWindow ignores the text argument. Am I supposed to always use > writeStatus ? The text argument is for the output on LCD display embedded in some braille displays. It's the untranslated (in terms of braille) text. The braille text is to be put in brl->buffer. writeStatus is completely something else: some displays have "status" cells, which are just a couple additional cells not usually used for displaying text, but for misc small information such as the cursor position. > It seems that the driver assumes that for USB devices it's assumed that > after isUsbDevice the device is equal to the USB serial. I thought of using > usb/<some id> to avoid costly scanning just to find out if a USB device > exists with given serial. Should I make isQualifiedDevice adjust device to > strip usb/ ? I'm not sure to understand that. > What are the functions usbReapResponse and usbSetAlternative are supposed to > do? I don't know and let Dave answer. Samuel _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
