Typo in kernel configuration (xconfig)

Typo in kernel configuration (xconfig)

[Danny Beaudoin]

Hi!
If I'm not at the right place, please forward this to the right person.

In Device Drivers/Graphics Support/Support for frame buffer devices:
"On several non-X86 architectures, the frame buffer device is the
only way to use the graphics hardware."

This should be 'x86' instead, as in the rest of the description.

Re: Typo in kernel configuration (xconfig)

[Randy.Dunlap]

Danny Beaudoin wrote:
> Hi!
> If I'm not at the right place, please forward this to the right person.
> 
> In Device Drivers/Graphics Support/Support for frame buffer devices:
> "On several non-X86 architectures, the frame buffer device is the
> only way to use the graphics hardware."
> 
> This should be 'x86' instead, as in the rest of the description.

Are you sure?  It makes sense to me the way it currently is...

-- 
~Randy

Re: Typo in kernel configuration (xconfig)

[Jesper Juhl]

On Sun, 12 Dec 2004, Danny Beaudoin wrote:

> Hi!
> If I'm not at the right place, please forward this to the right person.
> 
> In Device Drivers/Graphics Support/Support for frame buffer devices:
> "On several non-X86 architectures, the frame buffer device is the
> only way to use the graphics hardware."
> 
> This should be 'x86' instead, as in the rest of the description.
> 
I don't think you are right. On x86 the framebuffer is not your only 
option, and on some non-x86 archs (like alpha for instance - at least 
this used to be the case when last I had an alpha box), fb is the 
only option. I think the text is correct as it stands.

-- 
Jesper Juhl

Re: Typo in kernel configuration (xconfig)

[Espen Fjellvær Olsen]

On Mon, 13 Dec 2004 01:17:11 +0100 (CET), Jesper Juhl <juhl-lkml@dif.dk> wrote:
> I don't think you are right. On x86 the framebuffer is not your only
> option, and on some non-x86 archs (like alpha for instance - at least
> this used to be the case when last I had an alpha box), fb is the
> only option. I think the text is correct as it stands.
> 
> --
> Jesper Juhl

Maybe he ment the capitalization of the character, non-X86?
It should say non-x86.

-- 
Mvh / Best regards
Espen Fjellvær Olsen
espenfjo@gmail.com
Norway

Re: Typo in kernel configuration (xconfig)

[Randy.Dunlap]

Espen Fjellvær Olsen wrote:
> On Mon, 13 Dec 2004 01:17:11 +0100 (CET), Jesper Juhl <juhl-lkml@dif.dk> wrote:
> 
>>I don't think you are right. On x86 the framebuffer is not your only
>>option, and on some non-x86 archs (like alpha for instance - at least
>>this used to be the case when last I had an alpha box), fb is the
>>only option. I think the text is correct as it stands.
>>
>>--
>>Jesper Juhl
> 
> 
> Maybe he ment the capitalization of the character, non-X86?
> It should say non-x86.

Yes, I think he did.

Thanks.

-- 
~Randy

Re: Typo in kernel configuration (xconfig)

[Måns Rullgård]

Jesper Juhl <juhl-lkml@dif.dk> writes:

> On Sun, 12 Dec 2004, Danny Beaudoin wrote:
>
>> Hi!
>> If I'm not at the right place, please forward this to the right person.
>> 
>> In Device Drivers/Graphics Support/Support for frame buffer devices:
>> "On several non-X86 architectures, the frame buffer device is the
>> only way to use the graphics hardware."
>> 
>> This should be 'x86' instead, as in the rest of the description.
>> 
> I don't think you are right. On x86 the framebuffer is not your only 
> option, and on some non-x86 archs (like alpha for instance - at least 
> this used to be the case when last I had an alpha box), fb is the 
> only option.

My Alphas all have VGA graphics, with the standard text modes
available.  Some of the older models may have had other types of
graphics.

-- 
Måns Rullgård
mru@inprovide.com

Re: Typo in kernel configuration (xconfig)

[Jan Engelhardt]

> Hi!
> If I'm not at the right place, please forward this to the right person.
>
> In Device Drivers/Graphics Support/Support for frame buffer devices:
> "On several non-X86 architectures, the frame buffer device is the
> only way to use the graphics hardware."
>
> This should be 'x86' instead, as in the rest of the description.

What kind of typo is that?




Jan Engelhardt
-- 
ENOSPC

Re: Typo in kernel configuration (xconfig)

[Matan Peled]

Jan Engelhardt wrote:

>>Hi!
>>If I'm not at the right place, please forward this to the right person.
>>
>>In Device Drivers/Graphics Support/Support for frame buffer devices:
>>"On several non-X86 architectures, the frame buffer device is the
>>only way to use the graphics hardware."
>>
>>This should be 'x86' instead, as in the rest of the description.
>>    
>>
>
>What kind of typo is that?
>
>
>
>
>Jan Engelhardt
>  
>
A nit picking one :)


Besides, linux is case-sensitive, isn't it?

Re: Typo in kernel configuration (xconfig)

[Jan Engelhardt]

>> > If I'm not at the right place, please forward this to the right person.
>> > 
>> > In Device Drivers/Graphics Support/Support for frame buffer devices:
>> > "On several non-X86 architectures, the frame buffer device is the
>> > only way to use the graphics hardware."
>> > 
>> > This should be 'x86' instead, as in the rest of the description.
>> 
>> What kind of typo is that?

> A nit picking one :)
> Besides, linux is case-sensitive, isn't it?

Depends where you look. In the code (C), yes, but the docs, I doubt.


Jan Engelhardt
-- 
ENOSPC

[PATCH] Re: Typo in kernel configuration (xconfig)

[Jesper Juhl]

On Mon, 13 Dec 2004, Matan Peled wrote:

> Jan Engelhardt wrote:
> 
> > > Hi!
> > > If I'm not at the right place, please forward this to the right person.
> > > 
> > > In Device Drivers/Graphics Support/Support for frame buffer devices:
> > > "On several non-X86 architectures, the frame buffer device is the
> > > only way to use the graphics hardware."
> > > 
> > > This should be 'x86' instead, as in the rest of the description.
> > >    
> > 
> > What kind of typo is that?
> > 
> > 
> A nit picking one :)
> 

Well, in case anyone actually cares, here's a patch (at the end of the 
mail) to fix the nit. "x86" does seem to be in the majority compared to 
"X86" in the Kconfig help texts, I guess we might as well make it 
consistent..

> Besides, linux is case-sensitive, isn't it?
> 
Filesystems, yes. C source, yes. help text for kernel options, no.



Desc: [Documentation] Make Kconfig help texts use the term "x86" consistently.

Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk>

diff -ur linux-2.6.10-rc3-bk7-orig/arch/ia64/Kconfig linux-2.6.10-rc3-bk7/arch/ia64/Kconfig
--- linux-2.6.10-rc3-bk7-orig/arch/ia64/Kconfig	2004-10-18 23:55:27.000000000 +0200
+++ linux-2.6.10-rc3-bk7/arch/ia64/Kconfig	2004-12-13 20:53:05.000000000 +0100
@@ -14,7 +14,7 @@
 	default y
 	help
 	  The Itanium Processor Family is Intel's 64-bit successor to
-	  the 32-bit X86 line.  The IA-64 Linux project has a home
+	  the 32-bit x86 line.  The IA-64 Linux project has a home
 	  page at <http://www.linuxia64.org/> and a mailing list at
 	  <linux-ia64@vger.kernel.org>.
 
@@ -269,7 +269,7 @@
 config IA32_SUPPORT
 	bool "Support for Linux/x86 binaries"
 	help
-	  IA-64 processors can execute IA-32 (X86) instructions.  By
+	  IA-64 processors can execute IA-32 (x86) instructions.  By
 	  saying Y here, the kernel will include IA-32 system call
 	  emulation support which makes it possible to transparently
 	  run IA-32 Linux binaries on an IA-64 Linux system.
diff -ur linux-2.6.10-rc3-bk7-orig/arch/mips/Kconfig linux-2.6.10-rc3-bk7/arch/mips/Kconfig
--- linux-2.6.10-rc3-bk7-orig/arch/mips/Kconfig	2004-12-06 22:24:17.000000000 +0100
+++ linux-2.6.10-rc3-bk7/arch/mips/Kconfig	2004-12-13 20:53:25.000000000 +0100
@@ -1040,7 +1040,7 @@
 	  architectures supported by Linux and make the implementation of
 	  application programs easier and more portable; at this point, an X
 	  server exists which uses the frame buffer device exclusively.
-	  On several non-X86 architectures, the frame buffer device is the
+	  On several non-x86 architectures, the frame buffer device is the
 	  only way to use the graphics hardware.
 
 	  The device is accessed through special device nodes, usually located
diff -ur linux-2.6.10-rc3-bk7-orig/drivers/video/Kconfig linux-2.6.10-rc3-bk7/drivers/video/Kconfig
--- linux-2.6.10-rc3-bk7-orig/drivers/video/Kconfig	2004-12-06 22:24:43.000000000 +0100
+++ linux-2.6.10-rc3-bk7/drivers/video/Kconfig	2004-12-13 20:51:11.000000000 +0100
@@ -17,7 +17,7 @@
 	  architectures supported by Linux and make the implementation of
 	  application programs easier and more portable; at this point, an X
 	  server exists which uses the frame buffer device exclusively.
-	  On several non-X86 architectures, the frame buffer device is the
+	  On several non-x86 architectures, the frame buffer device is the
 	  only way to use the graphics hardware.
 
 	  The device is accessed through special device nodes, usually located

Re: [PATCH] Re: Typo in kernel configuration (xconfig)

[Jan Engelhardt]

>Well, in case anyone actually cares, here's a patch (at the end of the 
>mail) to fix the nit. "x86" does seem to be in the majority compared to 
>"X86" in the Kconfig help texts, I guess we might as well make it 
>consistent..

Hopefully nobody gets the idea of changing the CONFIG_X86 in Kconfig to 
CONFIG_x86 ...




Jan Engelhardt
-- 
ENOSPC