On Tue, 2013-06-18 at 09:20 +0100, Ian Campbell wrote: > > any idea about other tools > > like dmidecode which could give some info here? > Other than having a grep around in /sys and /proc for (caseinsensitive) > qnap not much springs to mind. Yeah, I've tried that before... nothing found.
> On x86 we could provide an empty default configuration and abstract the > initscript stuff a bit more to make it easier for people to configure by > hand. However before we do that I think we need to simply get the daemon > working at all on such platforms. Well as said... at least the A125 stuff works... Guenter Roeck commented that he thinks my ttyS0 is actually the UART of the IT87xxx ... but I tried many times to send it the commands like 0x50 or such... nothing happened... So perhaps the LEDs/etc are just not connected to the UART in my case. > At the moment it sounds like it isn't even possible to determine that > you are running on a QNAP device at all. Remember that once the package > exists on x86 people could try and install on a whitebox x86 server or > any random piece of hardware, we need to do the right (i.e. > non-destructive) thing in this case. Well do we anything really destructive? Sure we send stuff to some serial devices... but there are plenty other packages which do similar things and allow the user to shoot him into his feet if he's stupid... If we add a warning in the package description that this is really for QNAP devices only... it should IMHO be enough. > Even once we know it is a QNAP I don't think we can safely just probe > serial ports looking for things. Well... I would make the devices configurable and fully put it into the user's responsibility to set up a qcontrol.conf... > They are different byte sequences. Sure.. > If I had to guess I would say that > clear just writes all cells to blank and reset actually power cycles the > LCD and/or its controller. That's what I guessed as well... but it's also just guessing... > > > (rebooting is the only exception I'm aware of) > > I saw that pic_raw command... what's the matter with it? > It is from the QNAP drivers. We don't have that driver. Sorry I wrote unclear... I didn't meant the binary pic_raw itself,... but the reboot command it can send... and what you mentioned as the only exception... For the records, I've had started thread[0] on lkml, maybe Greg Kroah-Hartman will look into providing some driver... we'll see whether he finds time actually. Cheers, Chris. [0] http://thread.gmane.org/gmane.linux.kernel/1508763
smime.p7s
Description: S/MIME cryptographic signature
