Skip to contentSkip to conversation

Kernel Autoconfiguration utility v.0.9.1.2

ANNONCE Giacomo Catenazzi 4 participants 4 messages Feb 15, 2001

lore
Share & tools
lore
#0 lore raw

Hello!

I just release a new verion of kernel autoconfig.
The kernel autoconfiguration utility will help user to detect and configure the kernel. The detection is soft, thus no hangs!

It is still in test phase, thus now it prints only the proposed configuration. To change real configurations, I'm still waiting for a working CML2.

On my hardware database there are:

1007  pci cards
 111  devices (block and char)
  37  file systems
   7  console drivers
   8  net protocols
 511  resources strings.

+ some extra special detection.

Project homepage:
http://sourceforge.net/projects/kautoconfigure/

How to use: (now, testing phase)
unpack the files (better: in a new directory)

Quoted 1 line

bash autoconfigure.sh | less

check the output.
no super user privileges required!

I need some help:
- Some drivers detect pci in a strange way, I could not check every files.
Please check if your cards are included.
- Check, add extra detections

I will do:
- updates to the database when a new official kernel version is released
- interface with CML2 (partially done, but CML2-9.0.1 has still bugs)
- better 'CONFIG_*=N' handling (e.g. I will check is a drivers depends on PCI. If this PCI card is not found, I can safely tell you that the device is not in the box).
- generate inverse dependences.

Comments?

giacomo

PS. I have done the autodetection reading the source and not using
real hardware, thus ... no warranty.

PPS: This tools is designed mainly for newbies (in kernel compiling...),
thus I don't expect to have a real autodetection on very special machines. [But I expect in the future to do this :-) ]

#1 lore raw

Hi Giacomo,

one small remark, presence of the Philips SAA7146 doesn't mean presence of the Stradis video capture card. This multimedia bridge chip is very multipurpose device and can be used on very different cards (for example satellite DVB receivers).

Best regards.

Signature · 2 lines
Andrey Panin            | Embedded systems software engineer
[email protected]        | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
#2 lore raw
In reply to Giacomo Catenazzi

Good day, Giacomo,

Quoted 5 lines · Giacomo Catenazzi

How to use: (now, testing phase)
unpack the files (better: in a new directory)

Quoted 1 line

bash autoconfigure.sh | less

check the output.
no super user privileges required!

Nice work - that's a neat way to do it.
One detail; you appear to assume that bash2 is being used. If
bash1 is /bin/bash, one gets syntax errors. The following patch allows the script to run under bash1 and bash2, with no noticeable problems.

autoconfigure.sh renamed from autoconfigure.sh-0.9.1.2.orig +6 -6
@@ -109,7 +109,7 @@
 }
 function found () {
     local conf=CONFIG_$1
-    if [ "${!conf}" !=  "y" ]; then
+    if [ "${conf}" !=  "y" ]; then
 	define $1 y
     else
 	debug "$1=y"
@@ -117,7 +117,7 @@
 }
 function found_y () {
     local conf=CONFIG_$1
-    if [ "${!conf}" != "y" ]; then
+    if [ "${conf}" != "y" ]; then
 	define $1 y
     else
 	debug "$1=y"
@@ -125,7 +125,7 @@
 }
 function found_m () {
     local conf=CONFIG_$1
-    if [ "${!conf}" != "y"  -a  "${!1}" != "m" ]; then
+    if [ "${conf}" != "y"  -a  "${1}" != "m" ]; then
 	define $1 m
     else
 	debug "$1=m"
@@ -133,7 +133,7 @@
 }
 function found_n () {
     local conf=CONFIG_$1
-    if [ -z "${!conf}" ]; then
+    if [ -z "${conf}" ]; then
 	define $1 n
     else
 	debug "$1=n"
@@ -142,7 +142,7 @@
 }
 function provide () {
     local prov=PROVIDE_$1
-    if [ "${!prov}" !=  "y" ]; then
+    if [ "${prov}" !=  "y" ]; then
         eval "PROVIDE_$1=y"
 	debug "PROVIDE_$1"
     fi
@@ -188,7 +188,7 @@
     set `od -An -tx1 -v $f`
     x0=$1; shift   # make variables zero-based
     echo -n "${1}${x0},${3}${2}"
-    if [ "${14}" == "00" ]; then
+    if [ "${14}" = "00" ]; then
 	echo -n ",${45}${44},${47}${46}"
     fi
     echo ",${8};Class:${11}${10},${9}"
	I'm sure I'm missing the real reasons why the "${!" and "=="

syntaxes were used (I don't know what they do, as I stick to bash1 for portability), so my apologies in advance.
Cheers,
- Bill

---------------------------------------------------------------------------
"Mouse movement detected. Please reboot for changes to take
effect."
--------------------------------------------------------------------------
William Stearns ([email protected]). Mason, Buildkernel, named2hosts,
and ipfwadm2ipchains are at: http://www.pobox.com/~wstearns
LinuxMonth; articles for Linux Enthusiasts! http://www.linuxmonth.com
--------------------------------------------------------------------------

#3 lore raw

William Stearns <[email protected]> writes:

|> Good day, Giacomo,
|> 
|> On Thu, 15 Feb 2001, Giacomo Catenazzi wrote:
|> 
|> > How to use: (now, testing phase)
|> >   unpack the files (better: in a new directory)
|> >   > bash autoconfigure.sh | less
|> >   check the output.
|> >   no super user privileges required!
|> 
|> 	Nice work - that's a neat way to do it.
|> 	One detail; you appear to assume that bash2 is being used.  If
|> bash1 is /bin/bash, one gets syntax errors.  The following patch allows
|> the script to run under bash1 and bash2, with no noticeable problems.
|> 
|> --- autoconfigure.sh-0.9.1.2.orig	Wed Feb 14 15:37:30 2001
|> +++ autoconfigure.sh	Thu Feb 15 10:59:45 2001
|> @@ -109,7 +109,7 @@
|>  }
|>  function found () {
|>      local conf=CONFIG_$1
|> -    if [ "${!conf}" !=  "y" ]; then
|> +    if [ "${conf}" !=  "y" ]; then
|>  	define $1 y
|>      else
|>  	debug "$1=y"

This is plain wrong. ${!conf} and ${conf} are completely different things.

Andreas.

Signature · 4 lines
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
[email protected]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg