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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGngYiXXrrqGxTt339EP53tschLgZ82eRGvGifHQw6pg=C88+Q@mail.gmail.com>
Date:   Wed, 5 Dec 2018 10:39:56 -0500
From:   Sven Van Asbroeck <thesven73@...il.com>
To:     gregkh@...uxfoundation.org
Cc:     Sven Van Asbroeck <svendev@...x.com>, robh+dt@...nel.org,
        Linus Walleij <linus.walleij@...aro.org>,
        Lee Jones <lee.jones@...aro.org>, mark.rutland@....com,
        Andreas Färber <afaerber@...e.de>,
        treding@...dia.com, David Lechner <david@...hnology.com>,
        noralf@...nnes.org, johan@...nel.org,
        Michal Simek <monstr@...str.eu>, michal.vokac@...ft.com,
        Arnd Bergmann <arnd@...db.de>, john.garry@...wei.com,
        geert+renesas@...der.be, robin.murphy@....com,
        paul.gortmaker@...driver.com,
        sebastien.bourdelin@...oirfairelinux.com, icenowy@...c.io,
        Stuart Yoder <stuyoder@...il.com>, maxime.ripard@...tlin.com,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        devicetree <devicetree@...r.kernel.org>
Subject: Re: [PATCH v5 1/6] fieldbus_dev: add Fieldbus Device subsystem.

Hello Greg, thanks for the feedback!

On Wed, Dec 5, 2018 at 5:17 AM Greg KH <gregkh@...uxfoundation.org> wrote:
> And why is this a class and not just a "normal" device and bus?  Devices
> live on busses, not generally as a class.  Can your devices live on
> different types of busses (USB, PCI, etc.)?

This patchset can be a bit confusing, because it doesn't just add support for a
single fieldbus device - it proposes a general fieldbus subsystem.

Fieldbus devices from different vendors can sit on the usb, i2c, pci, etc.
buse, but they all register as a fieldbus device, via fieldbus_dev_register(),
and show up as a fieldbus class member.

Userspace can then enumerate all fieldbus devices connected to the system by
looking at the class. Without having to know which bus they happen to be
connected to.

If there is an abstraction in Linux that's a better fit, I'm very open to
making changes.

Sven

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ