Pete Popov <ppopov@mvista.com> writes:
> On Tue, 2004-01-13 at 10:07, Goswin von Brederlow wrote:
> > Hi,
> >
> > when compiling a kernel for my XXS1500 I allways ended up with a
> > kernel oops in the network driver (au1000eth.c).
> >
> > Finaly I checked the actual kernel source the running kernel was build
> > from and found "CONFIG_BCM5222_DUAL_PHY" was set. Setting that solves
> > the oops.
> >
> > Maybe that could be caught in some way and prevented.
>
> Well, the kernel shouldn't be crashing but as far as the BCM dual phy
> thing -- I'm not sure how to detect it at run time without knowing ahead
> of time that we've got one. I admittedly haven't spent too much time
> thinking about this problem but I didn't see an easy way to handle it.
>
> Pete
Maybe some
if (mach == MACH_XXS1500) ...
construct? The MACH_XXS1500 must be good for something.
Hopefully MyCable will change the name when they design a new board
with a different network thing.
MfG
Goswin
