Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1741491
| From | Krzysztof Kozlowski <krzk@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver |
| Date | 2017-09-28 14:30 +0200 |
| Message-ID | <uuG70-vR-31@gated-at.bofh.it> (permalink) |
| References | <uux3H-346-1@gated-at.bofh.it> <uuAuC-5iV-13@gated-at.bofh.it> <uuEyd-7SR-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Sep 28, 2017 at 12:43 PM, Linus Lüssing
<linus.luessing@c0d3.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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver Linus Lüssing <linus.luessing@c0d3.blue> - 2017-09-28 04:50 +0200
Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver Krzysztof Kozlowski <krzk@kernel.org> - 2017-09-28 08:30 +0200
Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver Linus Lüssing <linus.luessing@c0d3.blue> - 2017-09-28 12:50 +0200
Re: [PATCH] ARM: multi_v7_defconfig: Enable USB3503 driver Krzysztof Kozlowski <krzk@kernel.org> - 2017-09-28 14:30 +0200
csiph-web