linux-kernel - Re: Ethernet driver on 2.6.22

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070924154430.f19136e1.randy.dunlap@oracle.com>
Date:	Mon, 24 Sep 2007 15:44:30 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	hce <webmail.hce@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Ethernet driver on 2.6.22

On Tue, 25 Sep 2007 08:39:07 +1000 hce wrote:

> On 9/24/07, Randy Dunlap <randy.dunlap@...cle.com> wrote:
> > On Mon, 24 Sep 2007 12:40:07 +1000 hce wrote:
> >
> > > Thanks Randy.
> > >
> > > On 9/24/07, Randy Dunlap <randy.dunlap@...cle.com> wrote:
> > > > On Mon, 24 Sep 2007 08:52:36 +1000 hce wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I am upgrading from kernel 2.6.11 to 2.6.22 on ARM S3C2400A and found
> > > > > a following issue on 2.6.22.
> > > > >
> > > > > On 2.6.11, I selected CONFIG_ISA,  CONFIG_NET_PCI and CONFIG_CS89X0 to
> > > > > build  CS8900A Ethernet driver to kernel, it was running perfect.
> > > > >
> > > > > But on 2.6.22, I made the same configuration for CS8900A, the cs89x0.o
> > > > > could not be compiled in to the kernel (or as a module when I tried to
> > > > > CONFIG_CS89X0=m) unless I commented out depends statement in
> > > > > drivers/net/Kconfig. I double checked all three are CONFIG_ISA=y,
> > > > > CONFIG_NET_PCI=y and CONFIG_CS89X0=y. Any explanation please, was I
> > > > > missing something here?
> > > >
> > > > I didn't look in 2.6.11 Kconfig files, but in 2.6.22, this driver is
> > > > limited to 3 specific boards:
> > > >
> > > > config CS89x0
> > > >         tristate "CS89x0 support"
> > > >         depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
> > >
> > > The Kconfig for CS89x0 in 2.6.11 is exactly the same as 2.6.22.
> > >
> > > > Does ARM S3C2400A qualify as any of those?  (MACH_... or ARCH_...)
> > >
> > > I can run CS89x0 for ARM S3C2400 in 2.6.11, at least I can say yes,
> > > the ARM S3C2400A qualifies those in 2.6.11, I don't know the 2.6.22
> > > and I hope someone knows 2.6.22 well can answer it.
> > >
> > > > (latter: ARCH_PNX010X is not used anywhere else AFAICT)
> > >
> > > Yes, but you only need to enable ISA and NET_PCI to use CS89x0.
> >
> > Right.
> >
> > I don't have any problem building CS89x0 for X86_32:
> > make defconfig then enable ISA (what!?!?  why not in defconfig?)
> > and then enable CS89x0.
> 
> I don't have my embedded system here, I'll try when I get there. But,
> let me clarify it, did you mean to type "make defconfig" on linux
> (kernel) directory, and enable ISA, NET_PCI and CS89x0 from the
> prompt?
> 
> My procedure was to edit .config to enable ISA, NET_PCI and CS89x0
> from vim, then type "make menuconfig" and "make oldconfig" (The same
> procedure I did in 2.6.11 which works fine). Does that make things
> differently?

You should do "make oldconfig" immediately after editing the .config
file (AFAIK).  Or the "make menuconfig" might run the oldconfig
changes for you.

Then I would just double-check the final .config file
to make sure that it contains what you expect it to contain.

> > Please send your .config file.
> 
> I'll, but I don't have the system right now.

OK.

---
~Randy
Phaedrus says that Quality is about caring.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/