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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Tue, 5 Mar 2019 14:04:57 +0100
From:   "Enrico Weigelt, metux IT consult" <>
To:     LKML <>, X86 ML <>,, Borislav Petkov <>,
        "H. Peter Anvin" <>
Subject: guidelines on creating defconfigs

Hi folks,

I'd like to create a defconfig for the apuv2 board (pretty average
x86, but w/o display, instead a bit of extra gpio/leds, etc).

The big question for me now is: which non-hw-related things should
be included ?

IMHO, it seems clear that it should enable all drivers for all hw
the board actually has. But what about hw that can be plugged in ?
(eg. the board has several pcie and usb slots). Are there any things
that should be enabled by a defconfig ?

Another topic are things like filesystems, initrd, etc, etc.

So, I'd like to know whether there are some guidelines or at least
some consensus on what shall be included in a defconfig.



Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering -- +49-151-27565287

Powered by blists - more mailing lists