linux-kernel - Re: How to write driver that needs to call another driver?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100126214647.GA5616@rhlx01.hs-esslingen.de>
Date:	Tue, 26 Jan 2010 22:46:47 +0100
From:	Andreas Mohr <andi@...as.de>
To:	linux-kernel@...r.kernel.org
Cc:	Stanislav Brabec <utx@...guin.cz>
Subject: Re: How to write driver that needs to call another driver?

Hi,

dito here: I've got a nice ELV USB2I2C adapter which has a cp210x USB2serial
chip (i.e., drivers/usb/serial/cp210x.c) and is a definite I2C stack
driver candidate (i.e., drivers/i2c/xxx).

So???

Although I suspect that our two cases might be unrelated since yours
seems like lots of platform data magic and mine might perhaps be
solvable via some tty layer magic.

Sorry for the disruption ;)

Andreas Mohr
--
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/