From: Christian Volkmann <haveaniceday@cv-sv.de>
To: Claas Langbehn <claas@rootdir.de>
Cc: Simon Arlott <simon@fire.lp0.eu>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>
Subject: Re: Via C3/C7: other flags possible ?
Date: Sun, 20 May 2007 15:14:38 +0200 [thread overview]
Message-ID: <465049BE.5000000@cv-sv.de> (raw)
In-Reply-To: <4650047F.4000804@rootdir.de>
Bit 20 in edx is set if NX is available for C7:
eax in: 0x80000001, eax = 00000000 ebx = 00000000 ecx = 00000000 edx = 00100000
( from your posting "This kernel requires the following..." )
The official VIA Eden datasheet seems to be NDA. I have not found any
official download link on the pages:
http://www.via.com.tw/en/products/processors/c7/
The /c3/ pages contain the documentation for the C3 family.
I do not think the NX feature can be switched on/off by regular registers.
May be it helps to play around with the bios ?
Load "default settings" => see how the NX flag acts.
Load "optimized settings" => see how the NX flags acts.
I suppose the bios developer had used one setting to test and
work with the NX flag regular.
Christian
> If you read the other thread properly you'd see that the BIOS has an option to enable or disable it... when enabled it shows up.
PS: @Simon, sorry that I missed the other thread. Too much traffic
and not enough time for me to read all. I suppose that's a fulltime job ;-)
Claas Langbehn wrote:
> Simon Arlott schrieb:
>> On 19/05/07 23:36, Christian Volkmann wrote:
>>> Christian Volkmann wrote:
>>>> Claas asked for the NX flag for the Via C3 (?) processors
>>>> in another thread.
>>
>> If you read the other thread properly you'd see that the BIOS has an
>> option to enable or disable it... when enabled it shows up.
>
> Right, but my bios disables this after each boot-time :(
> Therefore it would be great if the kernel would not care
> about the BIOS and enable it anyway.
>
> This seems to be a severe bug in the BIOS, but VIA does not
> deliver a new BIOS since months. :(
>
>>
>> I can't reboot that box just to test cx8 detection (which is missing).
>>
> It works here.
>
>
>
> claas
>
next prev parent reply other threads:[~2007-05-20 13:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 0:09 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 Christian
2007-05-17 0:42 ` Dave Jones
2007-05-17 1:15 ` H. Peter Anvin
2007-05-17 1:55 ` H. Peter Anvin
2007-05-17 1:39 ` Christian
2007-05-17 21:28 ` Christian Volkmann
2007-05-17 21:47 ` Dave Jones
2007-05-17 21:59 ` Christian Volkmann
2007-05-31 5:22 ` [RFC: 2.6 patch] i386: remove support for the Rise CPU Adrian Bunk
2007-05-31 13:31 ` Dave Jones
2007-05-31 17:37 ` Christian Volkmann
2007-05-31 17:48 ` Dave Jones
2007-05-19 10:22 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 Hans de Bruin
2007-05-17 8:56 ` Alan Cox
2007-05-17 11:51 ` Andi Kleen
2007-05-17 15:02 ` Dave Jones
2007-05-17 22:14 ` H. Peter Anvin
2007-05-19 5:53 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 II Andi Kleen
2007-05-19 6:02 ` Dave Jones
2007-05-19 11:47 ` Andi Kleen
2007-05-19 17:23 ` Dave Jones
2007-05-19 8:22 ` Claas Langbehn
2007-05-19 18:10 ` H. Peter Anvin
2007-05-19 11:42 ` Christian Volkmann
2007-05-19 11:54 ` Andi Kleen
2007-05-23 21:50 ` H. Peter Anvin
2007-05-19 17:26 ` Claas Langbehn
2007-05-19 20:22 ` Via C3: other flags possible ? Christian Volkmann
2007-05-19 22:36 ` Christian Volkmann
2007-05-19 22:52 ` Via C3/C7: " Simon Arlott
2007-05-20 8:19 ` Claas Langbehn
2007-05-20 13:14 ` Christian Volkmann [this message]
2007-05-20 12:59 ` Via C3: " Andi Kleen
2007-05-19 17:54 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 II Claas Langbehn
2007-05-17 1:10 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 Linus Torvalds
2007-05-17 1:25 ` Christian
2007-05-17 2:21 ` Linus Torvalds
2007-05-17 3:05 ` H. Peter Anvin
2007-05-17 3:16 ` Linus Torvalds
2007-05-17 4:51 ` H. Peter Anvin
2007-05-17 6:18 ` Dave Jones
2007-05-17 6:31 ` H. Peter Anvin
2007-05-17 6:17 ` Dave Jones
2007-05-17 9:22 ` Hans de Bruin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=465049BE.5000000@cv-sv.de \
--to=haveaniceday@cv-sv.de \
--cc=ak@suse.de \
--cc=claas@rootdir.de \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.