linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Garcia <jpgarcia@execpc.com>
To: Derek Homeier <supas100@astrophysik.uni-kiel.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: switching consoles
Date: Fri, 14 Jul 2000 13:19:24 -0500	[thread overview]
Message-ID: <396F59AC.AD522F00@execpc.com> (raw)
In-Reply-To: Pine.SOL.3.95.1000714193210.28063B-100000@juliet


Derek Homeier wrote:
> Generally, however, I prefer to set the primary function of the F[1-12]
> keys to "Function keys" in the "Options" of the "Keyboard" Control Panel.
> BTW, this seems to be reset whenever my OF variables are set back to defaults.
> Does anyone know if it is possible to change this setting in OF directly?

I suppose you could try setting it back and forth and getting a hexdump of nvram
and then diff them to find the common thread.  then write an app that does it
for you.

Kinda brute force, but thats how I wrote setpramboot and got it working for my
PDQ. (http://www.execpc.com/~jpgarcia)  The F[1-12] keys thing could be as
little as a single bit, right?

--
Joseph P. Garcia      jpgarcia@execpc.com      jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate                      Student Employee - Systems Programmer
University of Wisconsin - Madison                            UW Lidar Group

Its not about MHz, its about who's got the bigger endian.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-14 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 17:33 switching consoles Derek Homeier
2000-07-14 18:19 ` Joseph Garcia [this message]
2000-07-18 20:29   ` Derek Homeier
2000-07-18 20:41     ` Joseph Garcia
2000-07-18 21:13       ` Derek Homeier
2000-07-18 21:22         ` Joseph Garcia
2000-07-18 21:50           ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2000-07-14  9:29 Iain Sandoe
2000-07-14 10:24 ` Martin Costabel

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=396F59AC.AD522F00@execpc.com \
    --to=jpgarcia@execpc.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=supas100@astrophysik.uni-kiel.de \
    /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 NNTP newsgroup(s).