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  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]
Date:   Thu, 22 Dec 2022 17:36:22 +0100
From:   Andrew Lunn <>
To:     Vladimir Oltean <>
Cc:     Rob Herring <>,
        Krzysztof Kozlowski <>,
        Florian Fainelli <>,
        Lee Jones <>,
        Colin Foster <>,
        Alexandre Belloni <>,,,
Subject: Re: Advice on MFD-style probing of DSA switch SoCs

> > Maybe the media subsystem has some pointers how to do this. It also
> > has complex devices made up from lots of sub devices.
> You mean something like struct v4l2_subdev_ops? This seems like the
> precise definition of what I'd like to avoid: a predefined set of
> subfunctions decided by the DSA core.
> Or maybe something else? To be honest, I don't know much about the media
> subsystem. This is what I saw.

Russell King put in some infrastructure where a media 'glue' driver
has a list of other drivers which need to probe and register there
resources with the kernel before it then becomes active and glues all
the parts together. I just know it exists, i've never used it, so i've
no idea if it could be useful or not.

What i'm really trying to say is that we should look outside of netdev
and see if similar problems have been solved somewhere else and all
that is needed is some code copying.


Powered by blists - more mailing lists