lkml.org 
[lkml]   [2007]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Kconfig variable "COBALT" is not defined anywhere
There were other patches which added more COBALT support, but they
were dropped or lost or whatever.

I would not balk at having that code yanked. I never got around to
doing proper Cobalt support for modern kernels. :(

On 6/3/07, Roland Dreier <rdreier@cisco.com> wrote:
> > > > there is no Kconfig file which defines the selectable option
> > > > "COBALT", which means that this snippet from drivers/char/nvram.c:
> > > >
> > > > # if defined(CONFIG_COBALT)
> > > > # include <linux/cobalt-nvram.h>
> > > > # define MACH COBALT
> > > > # else
> > > > # define MACH PC
> > > > # endif
> > > > never evaluates to true, therefore making <linux/cobalt-nvram.h>
> > > > fairly useless, at least under the circumstances.
>
> > > Maybe it should be MIPS_COBALT ?
>
> > that's the first thing that occurred to me, but that header file is
> > copyright sun microsystems and says nothing about MIPS, so that didn't
> > really settle the issue. that's why i'd rather someone else resolve
> > this one way or the other.
>
> Actually, looking through the old kernel history, it looks like this
> was added by Tim Hockin's (CCed) patch "Add Cobalt Networks support to
> nvram driver". Which added this to drivers/cobalt:
>
> +bool 'Support for Cobalt Networks x86 servers' CONFIG_COBALT
>
> I guess Tim can clear up what's intended...
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-06-03 23:11    [W:0.245 / U:0.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site