| 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: <4ae6feff-147e-3148-cde4-53039c96ea80@wirenboard.com>
Date: Sun, 12 Mar 2023 13:19:52 +0300
From: Evgeny Boger <boger@...enboard.com>
To: m.zatovic1@...il.com
Cc: airlied@...hat.com, andriy.shevchenko@...el.com, arnd@...db.de,
axboe@...nel.dk, benjamin.tissoires@...hat.com, bvanassche@....org,
dan.j.williams@...el.com, devicetree@...r.kernel.org,
dipenp@...dia.com, fmdefrancesco@...il.com,
furong.zhou@...ux.intel.com, gregkh@...uxfoundation.org,
jacek.lawrynowicz@...ux.intel.com,
krzysztof.kozlowski+dt@...aro.org, linus.walleij@...aro.org,
linux-kernel@...r.kernel.org, linux@...y.sk, masahiroy@...nel.org,
mathieu.poirier@...aro.org, mwen@...lia.com, ogabbay@...nel.org,
robh+dt@...nel.org, treding@...dia.com, yangyicong@...ilicon.com
Subject: Re: [PATCHv3 0/4] Wiegand bus driver and GPIO bitbanged controller
Hi Martin,
Thank you for you work! I'm currently working on Wiegand *receiver*
kernel driver, and hopefully we can make both sending and receiving
Wiegand implementation in kernel.
I tried to read all the discussion for the previous series, but still
don't quite understand why do we need the infrastructure to be that
complex. I mean Wiegand is point-to-point connection, so why do we even
need bus/controller/device abstractions at all? There will be always
just the single device per controller, right?
--
Kind regards,
Evgeny Boger
CTO @ Wiren Board
Powered by blists - more mailing lists