2 codec for playback.
The WinTV PVR-250 has no decoder. The WinTV PVR-350 (which
the OP referred to) does have one (but no Linux driver AFAIK):
http://www.hauppauge.com/html/chart.htm
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
yboard generates the raw
0xff keycode during the "missing" caps lock key up/down events. The
patch needs this for it to work. In drivers/macintosh/adb.c:adb_input(),
set "dump_adb_input" to 1 and watch your syslog when you press the
caps lock key. (You can do this at run tim
to be byteswapped/swabbed). Has this changed? If
c> not, then xmms-cdread is certainly broken since the code is just not there
c> to do the swabbing.
Yes, I think this was fixed in xmms-1.2.6 (although xmms-cdread
itself did not need to change).
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
way I got it to work on the TiBook. This is with xmms-1.2.5 and benh
kernels since 2.4.4.
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
hink you may have been
checking the keycode after the msb (which signifies key up/down) has
been stripped:
up_flag = (keycode & 0x80);
keycode &= 0x7f;
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
27;t seem to make a difference
whether or not you press other keys -- the same order of four keycodes
still gets generated for CapsLock. So for the clone keyboard, the
patch I've been using keeps track of the CapsLock key state, as you said.
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
ess/release events so you still need
something like "loadkeys" to remap to Control.) Yeah, it's still a
hack and we need something better.
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
--- drivers/macintosh/adbhid.c.orig Mon Aug 27 21:28:19 2001
+++ drivers/macintosh/adbhid.c Tue Au
r instances where
m> a response packet byte has the highest bit set? Otherwise reply[0]&0x80
m> would be a test to catch both.
I'm not sure I follow you but the highest bit normally
distinguishes between a key "press" and a key "release":
up_flag = (keycode & 0x80);
keycode &= 0x7f;
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
I think).
Well, I know of at least one other type of ADB keyboard where
this wouldn't work. The keyboard on my old PowerWave generates
different events for CapsLock:
1st press:0x39
1st release: 0x80
2nd press:0xb9
2nd release: 0x80
So that requires a different hack to get CapsLock to behave the
"right" way.
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
id = 2
2nd release:
Aug 27 19:39:52 localhost kernel: adb packet: 2c b9 ff, id = 2
So, I tried a quick hack in adbhid_input_keycode (drivers/macintosh/adbhid.c)
to translate the events appropriately and it seems to work (at last!).
Thanks a lot for the pointer!
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
For now, I've disabled the extra key events that the kernel
generates for the CapsLock key and am trying to train myself to
press and release once each time before typing a control character
sequence, but it clearly sucks.
--
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
ing for 12 hours used up about 42% of
the battery. With your latest kernel, it used up about 25%. (I
haven't measured it on MacOS yet.) Is that about what you would
expect?
Thanks.
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
ackground. Fortunately,
this goes away after the display is shut off for ~20 minutes either by
powering down or by sleeping with an older kernel.
Sorry for the non-technical description, but has anyone else
noticed this?
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
>>>>> On Tue, 10 Jul 2001 23:30:48 -0700, [EMAIL PROTECTED] (Gregorio Gervasio
>>>>> Jr.) said:
[ TiPB sleep problems with 2.4.6 ]
g> I get the same trace. As Olaf Hering suggested, it's failing
g> when "giveup_altivec" is call
24
bl msr_vec_debug /* debug thingy in process.c */
mtlrr24
blr
3:
...
I think PVR_7400 is the unshifted value? (Also, the TiPB uses a 7410,
so what is the right comparison?) Anyway, without this check, sleep
seems to be fine in both console and X11 mode.
Gregorio Gervasio, Jr.
[EMAIL PROTECTED]
15 matches
Mail list logo
