On Tue, 2013-07-02 at 01:27 +0200, Christoph Anton Mitterer wrote: > On Sun, 2013-06-30 at 16:30 +0100, Ian Campbell wrote: > > Which could be destructive, for all we know, since we don't know what is > > on the other end nor what it will do. > Well but AFAIU, right now you also just check for gpio_keys, right? And > anything else could have added that as well?!
No, we check /proc/cpuinfo for strings which are specific to particular classes of QNAP hardware, e.g. "QNAP TS-119/TS-219". > Also there is no guarantee that the order of ttyS0 / S1 is always the > same... On a given class of hardware there is, or at least there are GPIOs which we can check first (e.g. there is one which signal LCD present or not). > > It's all a bit moot until there is working support for at least one x86 > > platform though. > Well I don't see that coming unfortunately.... I mean the A125 is > working... so we could support at least that... but I couldn't get the > rest working via serial console (either I make something wrong... or it > simply doesn't work anymore)... and I really would have preferred that > over a real kernel modules. > You don't have any good contact at QNAP, do you? Unfortunately not really. > Well,... not sure if the A125 support is enough for you to build it for > non-arm... it think though it would be worth it. Yes, I may as well. Since I'll want to do some debconf stuff it will take me some time. Ian.
signature.asc
Description: This is a digitally signed message part
