From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gnu/linux CPU serial number control utility
Date: Tue, 25 Jan 2005 16:02:06 -0700 [thread overview]
Message-ID: <000301c50331$e45d5590$0d00a8c0@merlin> (raw)
In-Reply-To: <20050125032136.GA1894@romuald.net.eu.org>
The specs are definitely open, unless intel has undocumented instructions.
If you go to intel's web site, you can download processor documentation. One
of the parts has information about supported instructions and how they work.
--
A man is a fool if he has forgotten what it was to be young, as his
experience is worth nothing.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7
----- Original Message -----
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, January 24, 2005 8:21 PM
Subject: Re: gnu/linux CPU serial number control utility
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Joseph,
>
> a good idea. However, I don't know if the specs I'd need are open, and
> I myself don't know x86 assembly at this time, though I do want to
> learn it in the future.
>
> Greg
>
>
> On Mon, Jan 24, 2005 at 08:12:00PM -0700, Joseph C. Lininger wrote:
>> Greg,
>> I don't know of such a program, but I imagine it wouldn't be that hard to
>> write such an animal if one wanted to do so. I imagine it's just an
>> instruction or sequence of instructions that you pass to the CPU to
>> instruct it to disable this feature. Then as long as the kernel or some
>> other program doesn't reenable it, it would stay disabled. You'd probably
>> have to write it in asembly though, as the C functions don't provide
>> access
>> to that.
>> --
>> A man is a fool if he has forgotten what it was to be young, as his
>> experience is worth nothing.
>>
>> Joseph C. Lininger
>> jbahm@pcdesk.net
>> Verification: 5eab38a77ac40416e075be8f50607ff7
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFB9btA7s9z/XlyUyARArSSAKDFY8Ip2sLRKC8bsO2pq5dh8eVMjwCfS/dM
> M/LN43tuZs46JzAOq3wf68U=
> =7SCF
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Gregory Nowak
` Joseph C. Lininger
` Gregory Nowak
` Joseph C. Lininger [this message]
` Gregory Nowak
` Joseph C. Lininger
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='000301c50331$e45d5590$0d00a8c0@merlin' \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).