05:54 <aholler_> omg, this openelec people. they still enable hid2hci by default and now have disabled the udev-rules ...

06:00 <aholler_> and getty disappeared

15:22 <vpeter> aholler: more info for my device tree problem. I'm having working 3.10 kernel. But would like to use 3.14. So I copy device tree files from 3.10 to 3.14. But there were some incompatibilites with USB. In usb node there is clock binding and because of that usb is not recognized properly. But with this binding it doesn't boot.

16:17 <aholler> vpeter: don't copy the files, use git to merge just the changes

16:24 <aholler> vpeter: sorry, but I don't intend to write a bug for that hid2hci problem. If I would write a bug for every bug I know in some os soft, I couldn't do anything else.

16:29 <vpeter> I would merge if there would be only few differences. But they are very different. I'm waiting for some official response. Git issue: fair enough :)

16:31 <aholler> you could tell them too to add a getty in order to make it possible to use a serial console ;)

16:34 <vpeter> users don't need that. Devs can add this to autostart.sh :)

16:34 <aholler> no

16:35 <aholler> you'll have to rebuild busybox

16:35 <aholler> someone did some premature optimization#

16:35 <aholler> the root of all evil ;)

16:36 <vpeter> I'm executing /bin/sh </dev/ttymxc1 2>&1 >/dev/ttymxc1 &

16:37 <vpeter> and if CONFIG_GETTY would be enabled we get getty program?

16:38 <aholler> sure, busybox has such. and users need such, if other input like keyboard and mouse doesn't work because of the bugs with hid2hci and udev ;)

16:38 <vpeter> I see your problem now.

16:38 <aholler> and I'm not going to offer a login without pwd ;)

20:03 <vpeter> aholler: custom udev rules work in latest openelec beta and rc1.

20:03 <vpeter> https://github.com/OpenELEC/OpenELEC.tv/issues/3436

20:06 <sraue> aholler sorry i dont followed all the talk because i have problems with my isp today, whats the issue with ci2hid in openelec for you? afaik we need this for some logitech keyboards... and i remember some users had issues in the time we dont shipped the udev rule and the hci2hid binary...

20:51 <aholler> vpeter: I've seen that bug ;)

20:52 <aholler> sraue: hid2hci should never be enabled by default, especially not for logitech-keyboards

20:53 <aholler> because in hci-mode you need keys to use mice and keyboards.

20:54 <aholler> that means they already have to be paired.

20:54 <aholler> so by default the dongle should be left in hid-mode, because the dongle usually is already paired with keyboard.

20:55 <aholler> but bluez doesn't have keys, so if you enable hci-mode it means no keyboard works

20:55 <aholler> until it was paired with bluez

20:56 <aholler> I've already explained that in the two rh-bugs

20:59 <aholler> that just means users have to enable hid2hci themself.

21:05 <aholler> it's a bit complicated

21:06 <aholler> and unfortunately many users don't understand it, requesting enabling hid2hci by default, which is just wrong

21:32 <aholler> it's true that it has to be enabled in order to use the bt functionality of the dongle, but that should not be done without user interaction because it means connected keyboards and mice will not function anymore until they've got paired using bluez

21:33 <aholler> sorry, no idea how to explain it better