linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: [Fwd: Re: 2.4 - buttons, temperature, ictc]
Date: Tue, 17 Jul 2001 11:01:25 -0400	[thread overview]
Message-ID: <20010717110125.D22214@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 196 bytes --]

Oops, I pulled this off the list by hitting 'r' instead of 'L'.  ;-)
Ethan

-- 
If I've told you once, I've told you once
And once is all that you needed.
		-- The Refreshments, "Carefree"

[-- Attachment #1.2: Type: message/rfc822, Size: 1664 bytes --]

From: Michael Schmitz <schmitz@zirkon.biophys.uni-duesseldorf.de>
To: Ethan Blanton <eblanton@cs.ohiou.edu>
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Subject: Re: 2.4 - buttons, temperature, ictc
Date: Tue, 17 Jul 2001 16:56:33 +0200 (CEST)
Message-ID: <Pine.LNX.4.10.10107171651070.22917-100000@zirkon.biophys.uni-duesseldorf.de>

> > handle all this. That way, users could even customize the thing to get
> > particular functions mapped to keys :-)
>
> Yeah ...  Like I would *love* to make those function keys be FUNCTION
> KEYS and press fn if I want to change the backlight/etc ...  I don't
> know about you guys, but I change desktops with Alt+Fn *way* more
> often than I turn my backlight brightness up or down...

That's not what I meant - I think there's some magic word you tell the
keyboard controller to make the fn keys default.

Would you know the necessary ADB command by any chance, Ben?

	Michael


[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

                 reply	other threads:[~2001-07-17 15:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010717110125.D22214@localhost.localdomain \
    --to=eblanton@cs.ohiou.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).