linux-kernel - Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 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] [day] [month] [year] [list]

Message-ID: <CAJKOXPeN+Rtseaz+szF6-QFqq2kRYPVEwy+t8NTqO6VyefUiJg@mail.gmail.com>
Date:   Thu, 28 Sep 2017 14:22:03 +0200
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Linus Lüssing <linus.luessing@...3.blue>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-samsung-soc@...r.kernel.org, Kukjin Kim <kgene@...nel.org>,
        Russell King <linux@...linux.org.uk>,
        Tobias Jakobi <tjakobi@...h.uni-bielefeld.de>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver

On Thu, Sep 28, 2017 at 12:43 PM, Linus Lüssing
<linus.luessing@...3.blue> wrote:
> Hi Krzysztof,
>
> Thanks for your quick reply!
>
> On Thu, Sep 28, 2017 at 08:21:26AM +0200, Krzysztof Kozlowski wrote:
>> [...]
>> Anyway please define this as a module (unless it can't... but it
>> worked in my case).
>
> In that case you used an initrd, right? I see various cases of USB
> built-ins, like CONFIG_USB_STORAGE=y, CONFIG_USB_DWC2=y and so on in
> multi_v7_defconfig. So my impression was that multi_v7_defconfig was
> supposed to allow booting a rootfs from a USB storage device even
> without an initrd.

We use modules for multi_v7 as much as possible with that exception as
fair as I remember - no need of initramfs/initrd for boots. If this is
your intention, please mention this in commit message ("using usb3503
as builtin to provide boot from USB without initrd/initramfs").

Best regards,
Krzysztof