From: Hiroshi Miura <miura@da-cha.org>
To: Alexey Shinkin <alex@elesy.tusur.ru>,
Thaly Palanisamy <thalaps@gerg.tamu.edu>
Cc: "linux-kernel@vger kernel org" <linux-kernel@vger.kernel.org>,
cpufreq@www.linux.org.uk
Subject: bootup and cpufreq driver support for ZFx86 processor
Date: Wed, 24 Mar 2004 23:21:37 +0900 [thread overview]
Message-ID: <87u10e5nri.wl%miura@da-cha.org> (raw)
In-Reply-To: <1501881750.20040218104216@elesy.tusur.ru>
Hi, Alex and Thaly,
I wrote Cyrix/NatSemi MediaGX setup/driver in linux.
I can get ZFx86 CPU datasheet, and look at it,
it seems similar to MediaGX, I think .
But datasheets is not well informative.
I'm just start trying the CPUFreq driver
and setup cpu codes.
Can you wait and try testing my code?
And can you send me some informations?
I want results of 'lspci -v', dmesg of bootup, 'cat /proc/cpuinfo'.
I need a 'vendor id' and a 'cpuid' of that cpu which is not on a datasheet.
At Wed, 18 Feb 2004 10:42:16 +0600,
Alexey Shinkin wrote in LKML:
>
> hi!
>
> I am playing with Linux 2.6.0 on a PC-104 board with
> ZFx86 CPU - it is Cyrix core based 486. Kernel 2.4.18 detects the CPU
> as Cyrix Cx486DX2, but 2.6.0 says it is 486.
>
> I looked through /arch/i386/kernel/setup.c in 2.4.18 sources,
> /arch/i386/kernel/cpu/common.c in 2.6.0 sources and found the
> identify_cpu() function that seems to be working a bit incorrectly in
> 2.6.0.
>
> In 2.4.18 it checks if the CPU able to execute CPUID , if cannot - the
> id_and_try_enable_cpuid() is called, which identifies old Cyrixes and
> tries to turn on CPUID on some of them. Even if the CPU is not
> CPUID-capable,Cyrix is detected by test_cyrix_52div(), at least, the
> function fills x86_vendor & x86_vendorid fields in for Cyrixes. The
> fields are used later for vendor-specific initialization.
>
> In 2.6.0 identify_cpu() does not check CPUID-uncapable CPUs by
> test_cyrix_52div() and
> doesnt try to enable CPUID on them, so , further generic_identify()
> considers my CPU as usual 486, doesnt find vendor in get_cpu_vendor
> and after all default CPU init procedure is performed instead of
> vendor-specific.
>
> I understand that now people are more focused on newest P4's,
> Athlons64 etc , but I think that support for old CPUs also shouldnt be
> broken...
>
>
> --
> Best regards,
> Alex Shinkin
>
At Wed, 25 Feb 2004 14:33:18 -0600,
Thaly Palanisamy wrote on CPUFreq-devel ML:
>
> Hello,
> Does the cpufreq driver support the Zfx86 processor runnix Linux (2.4.21)?
> The ZFx86 is on a PC104 single board computer(Prometheus from Diamond
> Systems Corporation- DSC). I tried the DSC forum, but no one was aware of.
> I need to slow down the Zfx currently running at 100 MHz to save power.
> Can anybody help me?
> Thanks,
> Thaly
>
> --
> Thalapathy Palanisamy,
> Electronics Technician II,
> Geochemical and Environmental Research Group,
> Texas A&M University,
> College Station, TX -77845
> Ph: (979) 862-2323 x113
> Fax: (979) 862-1347
> www.gerg.tamu.edu
>
>
prev parent reply other threads:[~2004-03-24 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 4:42 2.6.0 doesn't recognize some Cyrix Cpus ? Alexey Shinkin
2004-03-24 14:21 ` Hiroshi Miura [this message]
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=87u10e5nri.wl%miura@da-cha.org \
--to=miura@da-cha.org \
--cc=alex@elesy.tusur.ru \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thalaps@gerg.tamu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®