1 |
#a11y is an accessibility hash tag you may run across on the internet. |
2 |
That covers assistive technologies like screen readers; refreshable |
3 |
braille displays, magnifiers, and similar other technologies I've been |
4 |
fortunate to have never needed to use for work on technology. |
5 |
The information you provided I think will help my next gentoo install go |
6 |
better in the kernel build phase thanks. |
7 |
|
8 |
|
9 |
On Wed, 6 Apr 2022, Jack wrote: |
10 |
|
11 |
> On 2022.04.06 14:51, Jude DaShiell wrote: |
12 |
> >I'm curious, with a system about to build a kernel does a command or |
13 |
> >command switch exist to tell the kernel build process to build the kernel |
14 |
> >in such a way that all hardware now enabled gets enabled in the build of |
15 |
> >the kernel? |
16 |
> Which pieces get built into the kernel (or as loadable modules) is controlled |
17 |
> by .config. To get the new kernel to include all the drivers/modules enabled |
18 |
> in the current kernel, you can "zcat /proc/config.gz > .config" in the new |
19 |
> /usr/src/linux. (That does assume the running kernel is built with the |
20 |
> parameters to create /proc/config.gz.) Then run "make oldconfig" (or one of |
21 |
> it's variants) to include new lines to .config. To see (a subset) of those |
22 |
> modules are actually used by existing hardware, do "lspci -k". I don't know |
23 |
> of any script to automatically parse that output, although I wouldn't be |
24 |
> surprised if there was one (or more.) Note hat probably won't include modules |
25 |
> used for usb devices, just the usb hubs. Currently loaded modules can be |
26 |
> listed with lsmod, but that doesn't include anything built in. |
27 |
> |
28 |
> Is a11y a typo, or just something I don't understand? If you mean to say (all |
29 |
> Y) Y to all kernel config questions, I believe there is a make option for the |
30 |
> kernel which will do that - but I'd have to read the docs for the details. |
31 |
> Also, while that's of use for a distro kernel (where you have no idea what |
32 |
> will be in PCs where it gets used) it will add lots of stuff to the kernel |
33 |
> that you are unlikely to ever use. What is your actual goal? |
34 |
> |
35 |
> Jack |
36 |
> |
37 |
> |