| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAHzZGEzxm4K6vo8srHjjmgbXiwk9xHsn6hF02sQnZ3vfOZQCzQ@mail.gmail.com> Date: Fri, 26 Aug 2011 06:28:40 +0200 From: Dawid Ciężarkiewicz <dawidc@...abs.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: linux-kernel@...r.kernel.org Subject: Re: Problem with writing virtual serial device driver. 2011/8/25 Alan Cox <alan@...rguk.ukuu.org.uk>: > The first question would be what error code you get when you try and open > your new device, that would tell you much, and help identify your problem. I don't get any error. I can open the device with minicom and everything appears to be fine but non of ops registered for the device get's called -- the device is not doing anything. The "dbg()" calls that I've put all around are not being triggered. The only time dbg() is printed is init function, which is successful. I have no clue what can be wrong. As the device is purly virtual I leave a lot of fields in the original structure empty so this might be a problem, but how do I know which ones should I fill with some dummy values? (if this would be a problem of course). -- Dawid Ciężarkiewicz B-Labs. http://b-labs.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists