On Wed, Nov 12, 2014 at 8:41 AM, Terje Froysa <[email protected]> wrote: > Thanks Charles, > > I appreciate your ideas. > I seem stuck "between a rock and a hard place" with very little substantial > experiences to collect from the communities. > > I will try a couple of permutations more before I may revert to using the > standard Linux drivers. > > I also got some comments from Xenomai (Gilles Chanteperdrix) below. > > Regards > Terje Froysa > > > At first sight, I would say that the omap_serial driver does not implement > the necessary support (probably some ioctls), for what setserial is trying > to do. > > I see several ways out: > > - implement the missing support in omap serial so that you can use the > "setserial none" command; > > - try and use the 8250 driver instead of the omap_serial driver, since the > omap serial devices are 8250 compatible, this driver supports the necessary > ioctls for the "setserial none" command to work. At some point in time, I > know using this serial driver for the kernel console worked, but I do not > know if it was by chance (u-boot enables the clock, so the driver does not > have to enable it), and if it still works;
Ironically, the "omap_serial" branched from the 8250 driver around 3 years ago, currently linux-omap developers are working on merging back to using the 8250 based driver in a future kernel version (with a big pile of patches).. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
