On 04/28/2015 08:11 PM, Robert Nelson wrote: > On Tue, Apr 28, 2015 at 6:29 PM, Peter Hurley <[email protected]> > wrote: >> On 04/23/2015 04:56 PM, rh_ wrote: >>> On Wed, 22 Apr 2015 13:25:26 -0500 >>> Robert Nelson <[email protected]> wrote: >>> >>>> On Wed, Apr 22, 2015 at 3:58 AM, >>>> <[email protected]> wrote: >>>>> Hi all. >>>>> Is dtb-rebuilder >>>>> git clone https://github.com/RobertCNelson/dtb-rebuilder >>>>> and >>>>> git checkout origin/3.19.x -b tmp >>>>> compatible with 4.0 kernel? >>>> >>>> The intial sync up of the 4.0.x branch is now out.. >>>> >>>> The biggest delta, ttyOx -> ttySx transition for the serial port.. >>> >>> Why was this done, again. Didn't we go to ttyS before. This is bad >>> dejavu. Not the good kind. >> >> Different driver. >> >>> There is this: >>> >>> SERIAL_8250_OMAP_TTYO_FIXUP >>> >>> but still have to make host changes >>> >>> Maybe I'm missing something but if you want to boot into >>> different kernels this is a PITA. >> >> The omap-serial driver (aka, ttyOx) still works. TBH, I'm not >> sure why Robert switched to the omap_8250 driver so soon, because >> the userspace breakage was to be expected. > > The v3.8.x tree is still /dev/ttyOx ;)
Oh, it doesn't bother me; I reviewed the 8250_omap driver for inclusion in mainline. > I was going to phase it in on mainline, but then ti made the switch on > their v3.14.x-ti tree... I hate vendor trees. > So we bit the bullet. > > For systemd users, systemd fixed it up on boot.. > > For udev users, we now having working /dev/ttySx -> /dev/ttyOx rule... That works. What systemd does is parse the list of consoles emitted by the tty core to sysfs in /sys/class/tty/console/active and start getty on those. > For everything else... We i didn't test.. ;) > > If it's any consolation, i did yell at the developers on linux-omap, > how "fxxxd" up this was, specially since i was here during the ttyS -> > ttyO mess. I'm sorry I missed your email. > But i think we are now ready in 26-ish+ kernel releases to move back > to ttyO... ;) Hopefully before then, we'll have a namespace solution that will allow pain-free serial driver migrations (and allow multiple drivers to share the ttyS namespace). Regards, Peter Hurley -- 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.
