Re: mouseemu
On Mon, 27 Mar 2006 14:23:11 +0200 (CEST), Michael Schmitz [EMAIL PROTECTED] said: The state of the modifier key is kept by the X server, so you need to send the modifier before you send a regular key event (disregarding mouse events for a moment here). We could postpone the modifier event until we know what other event follows, but that's equally messy. I kind-of worked out a state machine to do this sort of thing; the result was horrible. Later on today I will have at look at the behaviour of Apple X11, and check out what events it is generating. Right, they must have solved this some way already. Yep, it just seems to send a modifier-up, button-click, modifier-down when the mouse is clicked. Should not really happen, because mouseemu intercepts all input events hopefully, and hence can ensure they get sent in the correct order. Meaning you cannot sneak a key event in between the mod up, mouse down, mod down sequence. IIRC X doesn't mind if the modifier state changes while a button is kept down. Either way, there's limits to what extent you can emulate mouse buttons using modifier keys. I'll cook up some experimental hack for you to test. That would be really cool! -- http://www.fastmail.fm - Does exactly what it says on the tin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wanted: Debian Installer PowerPC porter(s)
The reply below was only sent to the d-boot list; forwarding to d-powerpc as I would guess Brian is not subscribed to d-boot. -- Forwarded Message -- Subject: Re: Debian Installer PowerPC Date: Wednesday 29 March 2006 10:12 From: Geert Stappers [EMAIL PROTECTED] To: debian-boot@lists.debian.org On Tue, Mar 28, 2006 at 10:53:44PM -0800, brian morris wrote: hi - i am getting pretty worn out myself putting Debian on a new world mac for first time lately, a G4. i have thinking now it it is a hassle. i think the installer is over automated and that increase bug problems. for instance. Default boot of D-I activates the knowledge that is in the installer, all the default answers are sane well thought decisions. You can make the decisions yourself by booting expert a) the partitioning scheme and type i was given were not much at all to my liking or need. i was not given any option to correct this only take it or leave it. i was not told that journaling was being turned on. since the partition sizes i was given were not suitable i am force to resize later. Even booted default you get the choice to choose between * Whole disk * Largest free space * Manual partitioning 'Manual partitioning' gives you the freedom to partition as _you_ want. my backup drive here is firewire and i am hearing it won't boot a backup. (the backup i made on scsi with the old world machine wouldn't boot either, but i was able to run parted by interrupting the installer - although it no longer tells you you can i guess you can ... ) That has been reported before and even filled in a bugreport. I don't known which BR number nor it's actual state. That means that it might even be done at least it is on the to do list. on more general : i for one am no windows guy. I trained on unix back in the old days and now i am 50% mac at least. i like macs, and i like unix. i can't stand windows. i really can't. is this worth it. i have done some work with Fink project/ macosx.2 jaguar. obviously it it non-free. i don't like that but i need to do some pre-production sorts of work. by the way fink commander is compared to synaptic much better ! ?suggestions ?? SMILE The Debian-Installer only looks over automated. Please have a closer look at D-I and see why it is appricated by many others. Cheers Geert Stappers --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wanted: Debian Installer PowerPC porter(s)
On Wed, Mar 29, 2006 at 03:00:19AM +0200, Sven Luther wrote: - various old-world issues, including the work to free miboot, and inclusion of the free miboot version into the official archive. Mmm, i hope Colin Watson doesn't forget to add miboot support to his daily builds, or oldworld support will have been definitively killed. What do I need to do? (If at all possible, I'd prefer to produce a separate build for oldworld until such time as miboot is free, rather than having non-free material in the main daily build used on Debian CDs.) -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound on quad powermac/latest powerbooks/imacs
How can I find that out?
Try loading my driver, specifically snd-aoa-codec-onyx :P
Or dive into the device tree, find the layout-id property, and cross
reference it with the layout id in the Info.plist file from
AppleOnboardAudio.
Well, I didn't know where to get the Info.plist file (I only have Linux
installed). So I asked somebody with MacOS on the same hardware and the
information for audio is:
Built In Sound Card:
Devices:
Burr Brown PCM3052
Inputs and Ouputs:
Controls: Mute,Master
Playthrough:No
PluginID: Onyx
And so it goes on ... Onyx shows as the pluginID for all.
My driver will most likely not be able to handle it out of the box,
since the layout id is unknown to it, so you'd have to add it to
snd-aoa-fabric-layout.c
The layout-id was 0x56, so I added this:
/* PowerMac8,2 */
{ .layout_id = 86, .codecs[0] = onyx, .codecs[1] = topaz },
and I added the alias too.
johannes
Then built and loaded I loaded the modules and this is what I got:
Mar 29 13:26:17 mapache kernel: i2sbus: mapped i2s control registers
Mar 29 13:26:17 mapache kernel: i2sbus: control register contents:
Mar 29 13:26:17 mapache kernel: i2sbus:fcr0 = 0x856
Mar 29 13:26:17 mapache kernel: i2sbus:cell_control = 0x5b43b71a
Mar 29 13:26:17 mapache kernel: i2sbus:fcr2 = 0xe703
Mar 29 13:26:17 mapache kernel: i2sbus:fcr3 = 0x7200d607
Mar 29 13:26:17 mapache kernel: i2sbus:clock_control = 0x0
Mar 29 13:26:17 mapache kernel: i2sbus: found i2s controller
Mar 29 13:26:17 mapache kernel: ** pmf_call_one(/[EMAIL
PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/cell-enable) **
Mar 29 13:26:17 mapache kernel: ** pmf_call_one(/[EMAIL
PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/enable) **
Mar 29 13:26:17 mapache kernel: ** pmf_call_one(/[EMAIL
PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/clock-enable) **
Mar 29 13:26:17 mapache kernel: serial format: 0x4119
Mar 29 13:26:17 mapache kernel: dws: 0x2000200
Mar 29 13:26:17 mapache kernel: snd-aoa: found bus with layout 86 (using)
Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: found k2-i2c, checking if
onyx chip is on it
Mar 29 13:26:17 mapache kernel: low_i2c:xfer() chan=0, addrdir=0x47, mode=4,
subsize=1, subaddr=0x43, 1 bytes, bus /[EMAIL PROTECTED],f200/[EMAIL
PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]
Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_addr, isr: 6)
Mar 29 13:26:17 mapache kernel: low_i2c:KW: NAK on address
Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 6)
Mar 29 13:26:17 mapache kernel: KW: wrong state. Got KW_I2C_IRQ_ADDR, state:
state_stop (isr: 06)
Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 4)
Mar 29 13:26:17 mapache kernel: low_i2c:xfer error -5
Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: failed to read control
register
Mar 29 13:26:18 mapache kernel: low_i2c:xfer() chan=11, addrdir=0x93, mode=4,
subsize=1, subaddr=0x0, 2 bytes, bus /[EMAIL PROTECTED],0/[EMAIL
PROTECTED]/[EMAIL PROTECTED]
Anything else to try? The following related modules were loaded:
snd_aoa_codec_onyx 13264 0
snd_aoa_fabric_layout 7972 0
snd_aoa10448 2 snd_aoa_codec_onyx,snd_aoa_fabric_layout
i2sbus 23872 0
soundbus 11972 2 snd_aoa_fabric_layout,i2sbus
snd_pcm 138060 1 i2sbus
snd_timer 38248 1 snd_pcm
snd_page_alloc 16232 1 snd_pcm
snd94648 4 snd_aoa,i2sbus,snd_pcm,snd_timer
soundcore 15344 1 snd
Eduardo.
PD: I'm using kernel 2.6.16-rc1 on PowerMac 8,2 with a couple of patches from
Ben and, as you see, the i2c debugging information on.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Thermal control for PowerMac 8,2 and new snd module already included in the kernel?
I remember I had to patch 2.6.16-rc1 with a Ben patch to get the thermal control running. But the sound was broken and hung the computer. So, I'd like to know if I have to apply any patches to the latest available kernel in order to get both the thermal control and avoid the system hang when trying to access the sound module. You shouldn't need to with 2.6.16. There is also a new sound driver in the works though it's not upstream yet. Is it ready for testing? Will I needed it with the new snd-aoa driver? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound on quad powermac/latest powerbooks/imacs
You might want to load soundcore first. Or install the modules and do a depmod -a and then modprobe instead of insmod. I had the same problem. Sadly, up until 2.6.15 loading up soundcore hangs my imac so I haven't been able to go past that ... Its snd-powermac that hangs your imac, not soundcore I think You're right! Thanks to your comment I was able to test the new snd-aoa drivers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sound on quad powermac/latest powerbooks/imacs
On Wed, 2006-03-29 at 13:29 +0200, Eduardo Trápani wrote: Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: found k2-i2c, checking if onyx chip is on it Mar 29 13:26:17 mapache kernel: low_i2c:xfer() chan=0, addrdir=0x47, mode=4, subsize=1, subaddr=0x43, 1 bytes, bus /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_addr, isr: 6) Mar 29 13:26:17 mapache kernel: low_i2c:KW: NAK on address Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 6) Mar 29 13:26:17 mapache kernel: KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06) Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 4) Mar 29 13:26:17 mapache kernel: low_i2c:xfer error -5 Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: failed to read control register Mar 29 13:26:18 mapache kernel: low_i2c:xfer() chan=11, addrdir=0x93, mode=4, subsize=1, subaddr=0x0, 2 bytes, bus /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED] Anything else to try? The following related modules were loaded: Looks like it is on another i2c address or bus on those machines. Bugger. I have no idea how to find out which one. johannes signature.asc Description: This is a digitally signed message part
Re: sound on quad powermac/latest powerbooks/imacs
On Wed, 2006-03-29 at 10:23 +1100, Benjamin Herrenschmidt wrote: Why not use plain git ? I think cogito is pretty much deprecated nowadays no ? Dunno. I guess git-clone works too and I can happily use cg without telling anyone. Not that there's a particular reason I use cg.. :) johannes signature.asc Description: This is a digitally signed message part
Re: Thermal control for PowerMac 8,2 and new snd module already included in the kernel?
On Wed, 2006-03-29 at 13:32 +0200, Eduardo Trápani wrote: You shouldn't need to with 2.6.16. There is also a new sound driver in the works though it's not upstream yet. Is it ready for testing? Will I needed it with the new snd-aoa driver? I think Ben was talking about snd-aoa :) johannes signature.asc Description: This is a digitally signed message part
Re: snd-aoa: new apple sound driver
On Wed, 2006-03-29 at 15:01 +1100, Benjamin Herrenschmidt wrote: BTW.. with the current stuff, if I install the modules and then do modprobe i2sbus I get a registration error in dmesg. Hmm. What's the error? Can't reproduce this at all. Also, what machine? It works fine on my powermac, even when i2sbus is auto-loaded due to binding to the macio i2s device alias. If I then try to rmmod it, the machine blows up. Haven't had time to track that down at this point. That sucks. Appart from that, it works and I can play morse with myh SPID output :) Heh yeah, we did that too :) Oh, and jackd seems to be unhappy even if I tell it to ignore the capture channels, it's probably a problem with setting the sample formats, I haven't looked in detail (yet). Hmm. I'll try to see what jackd does. johannes signature.asc Description: This is a digitally signed message part
Re: snd-aoa: new apple sound driver
On Wed, 2006-03-29 at 10:40 +1100, Benjamin Herrenschmidt wrote: The GPIO stuff is a bit can-of-worms-ish ... we need at least 2 different implementations for machines using old style direct GPIO access and machines using platform functions. So we may need a gpio driver with 2 instances there. Yeah, was thinking like that too. I think we need to hook that with the input/output net... basically we just say things like mute/unmute(id) and the gpio layer sort of matches the input/output id with whatever gpios it has at hand. That's also why I think your input/output IDs should have separate entries for combo connectors vs. analog line out (at least you used not to, I haven't looked at the latest code). Note sure what you mean here... Then, the core would get events from interrupts (or clock switches from the codecs) via a yet-to-be-defined call and would react by calling the various mute/unmutes accordingly for available inputs and outputs on the bus where the event occured. Ah but you see, the codec actually mutes the digital output when it isn't usable, and the codec also mutes the analog output when we transfer compressed data. We don't amp-mute in that case, but just from the codec, so no analog audio is even leaving the codec. For things like headphone/speaker automute, I think we need a kind of tristate.. either that, or we need a bit mask of mute conditions. When any of them is set, it's muted. That way, the user mute control sticks regardless of the automute action or temporary mute to analog outputs because, for example, the digital input lost its clock and we are switching (we need to mute to avoid clics). Yeah. I have to think a bit about an in-snd-aoa api for all this. Hrm... So my feature calls are doing too much at once... (they both do the clocks and the cell enable). I don't do clock refcounting like Apple does tho, thus the main clock sources are always enabled. So I think all you have to do is toggle the I2Sn_CLK_ENABLE bits ... Hmm. How do I get at those bits? Clock refcounting would be nice too, along with proper power save management... Can you verify if all machines that have digital inputs (thus all machines for which you may need to do that kind of clock switching) also have working platform functions for doing so ? If they do, then it's really just a matter of calling those. If not, then we can either ioremap the FCR's in the driver and play with them (evil solution + possibly locking problems) or add a feature call. The former isn't feasible since I need to do clock switching even on analog-only machines to support more sample rates than the 44.1 KHz that the firmware sets for the boing sound :) In the later case, you add a feature call in pmac_feature.h and the appropriate entry in the table in feature.c and then you can toggle bits as you wish with appropriate locking (look at eixsting code in there). I can give you more details on irc if you need. Ok. I definitely need more details I think. But it would be nice if it could all be done with platform functions instead. Hardly possible though, see above. Modalias situtation. I played some tricks: i2sbus depends on soundbus Yeah :) There might be some issue with the macio automatching from userland, not sure yet, could just be missing bits in hotplug scripts. macio automatching is working, i2sbus loads, but the latter modules don't. I guess there's a userland issue in that it doesn't pick up new devices that are added to /sys while it is loading another module. Recording. There's code to record sound, but it doesn't do anything on my machine. I have no idea why. What machine ? The quad ? maybe you need some gpio manipulation or maybe you just didn't get something right in onyx ... I'll try later. Yeah the quad. I was thinking that no matter what, I should at least be recording silence, but my userland app (arecord) doesn't get *any* data at all. It's like the dbdma controller isn't doing anything. - macio_device gets the suspend resume event. That is, the i2s busses basically. That code should forward to all attaches sub-busses which then dispatch to codecs. right. - ordering of things should be: mute all, stop alsa, stop codecs (enable whatever internal power management mode they may have), stop clocks, disable i2s cells. yeah. It's slightly more complicated unless we assume that the control interface (i2c) is always available, because we'd also get power management through the i2c device stuff. I'll play with adapting the whole stuff to older machines, I have plenty of those :) We also need to implement a davbus module, so make sure you don't have too much i2s-related assumptions in your core.. No timeframe for that though, I'm fairly busy with other things at the moment I don't think there are any i2s assumptions. Well, except that on any given soundbus_dev, you have at most one input and one output stream... It's also a complicated thing
Re: Wanted: Debian Installer PowerPC porter(s)
On Wed, Mar 29, 2006 at 11:50:04AM +0100, Colin Watson wrote: On Wed, Mar 29, 2006 at 03:00:19AM +0200, Sven Luther wrote: - various old-world issues, including the work to free miboot, and inclusion of the free miboot version into the official archive. Mmm, i hope Colin Watson doesn't forget to add miboot support to his daily builds, or oldworld support will have been definitively killed. What do I need to do? Install the miboot package from http://people.debian.org/~luther/miboot on the buildd. (If at all possible, I'd prefer to produce a separate build for oldworld until such time as miboot is free, rather than having non-free material in the main daily build used on Debian CDs.) bah, if you want, i actually always thought that having the miboot builds in non-free would be best, bu t this idea was coldly received (at the sarge time though). We need to build non-free installer images anyway, for the non-free modules/firmware scenario anyway, so this would be a good test to make this possible later. In this case we can upload miboot to non-free, and see if it can pass, the only problem is that we don't really have the distribution right for the apple boot block, but i kind of doubt apple will ever be bothered to give it. That said, since apple provides tools to create bootable floppies including this boot block, we only need to see the licence of those tools. I fear though that back in those times, the idea of providing a licence for a mere bootblock was kind of not so present, and i believe our usages clearly falls in the fair-use scenario. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge installer for Mac Performa 6400/180 with 16MB RAM?
On 3/20/06, Simon Vallet [EMAIL PROTECTED] wrote: On Mon, 20 Mar 2006 14:03:23 +0100 Hans Ekbrand [EMAIL PROTECTED] wrote: No need for BootX (and with 16 MB RAM, the HD is probably small too, so avoiding BooX seems preferable). My recommendation is boot floppies from woody and boot the installed system with quik. Thats how I installed on my Performa 5400 with 24 MB RAM. Hi. We can install woody on this machine, but when we try to create the bootdisk (at the end of the installation) the installer says that the disk cannot be created. So we install quik and then reboot the machine. I agree on the BootX overhead, however be aware that the 6400 will nost likely *not* boot from OF with 'screen' as output-device -- you'll need to use a third party video adapter or a serial console When we reboot the machine (after the initial stage of the woody installation) there's nothing in the screen and we have to recover using command + option + p + r. I guess We've been warned. What does *not* boot from OF mean? Thanks. -- http://arhuaco.org/
How can I get rid of the starting bong! (G4-mac mini)?
Hi! Mi G4 mac mini, following apple tradition, starts with a noisy bong!. This is a real nuissance for me; I've talked to him, but to no avail... Googling I found this app, for MacOS X: http://www5e.biglobe.ne.jp/~arcana/software.en.html but no MacOS X is installed in my mac, only etch. Next step is asking to them about how the app works (I got their email); but I tought of asking here first, and maybe coordinate efforts, etc. Obvious stuff I tried: . The bong sounds even if headphones are plugged. Through the internal speaker, I mean. . Tried to press [mute] key before pressing the power button, but this is a usb happy hacking, not an ADB mac keyboard... . Tried setting the volume to 0 before shutting down the beast. No avail. Speakerectomy apart, do you know any way to disable this bong? Any OpenFirmware variable that can be set? (I've looked for it, too, but no luck either). I tell you that this is troublesome for me: I live in an old building; the walls are very thin..., and due to the (bad) architecture of the building, the bong can be heard by, virtually, everyone. Specially at night. I can hear clearly the conversations of at least three different neighbours... Thank you, Pancho. -- Pancho Horrillo To be conscious that you are ignorant is a great step to knowledge. Benjamin Disraeli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
On Wed, 2006-03-29 at 15:39 +0200, Pancho Horrillo wrote: Mi G4 mac mini, following apple tradition, starts with a noisy bong!. This is a real nuissance for me; I've talked to him, but to no avail... nvsetvol 0 johannes signature.asc Description: This is a digitally signed message part
Re: How can I get rid of the starting bong! (G4-mac mini)?
On Wed, 2006-03-29 at 15:39 +0200, Pancho Horrillo wrote: Hi! Mi G4 mac mini, following apple tradition, starts with a noisy bong!. [...] Speakerectomy apart, do you know any way to disable this bong? Any OpenFirmware variable that can be set? (I've looked for it, too, but no luck either). does nvsetvol 0 work for you? regards, wrobell [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
On 3/29/06, Pancho Horrillo [EMAIL PROTECTED] wrote: Hi! Mi G4 mac mini, following apple tradition, starts with a noisy bong!. This is a real nuissance for me; I've talked to him, but to no avail... Googling I found this app, for MacOS X: http://www5e.biglobe.ne.jp/~arcana/software.en.html but no MacOS X is installed in my mac, only etch. Next step is asking to them about how the app works (I got their email); but I tought of asking here first, and maybe coordinate efforts, etc. Obvious stuff I tried: . The bong sounds even if headphones are plugged. Through the internal speaker, I mean. . Tried to press [mute] key before pressing the power button, but this is a usb happy hacking, not an ADB mac keyboard... . Tried setting the volume to 0 before shutting down the beast. No avail. Speakerectomy apart, do you know any way to disable this bong? Any OpenFirmware variable that can be set? (I've looked for it, too, but no luck either). I use the command nvsetvol from the package powerpc-utils on my ibook. nvsetvol 0 will turn it off, but I like nvsetvol 1. Regards, Bin I tell you that this is troublesome for me: I live in an old building; the walls are very thin..., and due to the (bad) architecture of the building, the bong can be heard by, virtually, everyone. Specially at night. I can hear clearly the conversations of at least three different neighbours... Thank you, Pancho. -- Pancho Horrillo To be conscious that you are ignorant is a great step to knowledge. Benjamin Disraeli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
snd-aoa on PowerMac 8,2
Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: found k2-i2c, checking if onyx chip is on it Mar 29 13:26:17 mapache kernel: low_i2c:xfer() chan=0, addrdir=0x47, mode=4, subsize=1, subaddr=0x43, 1 bytes, bus /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_addr, isr: 6) Mar 29 13:26:17 mapache kernel: low_i2c:KW: NAK on address Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 6) Mar 29 13:26:17 mapache kernel: KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06) Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 4) Mar 29 13:26:17 mapache kernel: low_i2c:xfer error -5 Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: failed to read control register Mar 29 13:26:18 mapache kernel: low_i2c:xfer() chan=11, addrdir=0x93, mode=4, subsize=1, subaddr=0x0, 2 bytes, bus /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED] Anything else to try? The following related modules were loaded: Looks like it is on another i2c address or bus on those machines. Bugger. I have no idea how to find out which one. Would the tarball of device-tree help? There must be a way ... Is the address of the onyx codec hardwired in your code? Eduardo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: snd-aoa on PowerMac 8,2
On Wed, 2006-03-29 at 16:57 +0200, Eduardo Trápani wrote: Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: found k2-i2c, checking if onyx chip is on it Mar 29 13:26:17 mapache kernel: low_i2c:xfer() chan=0, addrdir=0x47, mode=4, subsize=1, subaddr=0x43, 1 bytes, bus /[EMAIL PROTECTED],f200/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_addr, isr: 6) Mar 29 13:26:17 mapache kernel: low_i2c:KW: NAK on address Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 6) Mar 29 13:26:17 mapache kernel: KW: wrong state. Got KW_I2C_IRQ_ADDR, state: state_stop (isr: 06) Mar 29 13:26:17 mapache kernel: low_i2c:kw_handle_interrupt(state_stop, isr: 4) Mar 29 13:26:17 mapache kernel: low_i2c:xfer error -5 Mar 29 13:26:17 mapache kernel: snd-aoa-codec-onyx: failed to read control register Mar 29 13:26:18 mapache kernel: low_i2c:xfer() chan=11, addrdir=0x93, mode=4, subsize=1, subaddr=0x0, 2 bytes, bus /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED] Anything else to try? The following related modules were loaded: Looks like it is on another i2c address or bus on those machines. Bugger. I have no idea how to find out which one. Would the tarball of device-tree help? There must be a way ... Dunno. You can mail it to me privately and I'll have a look. Is the address of the onyx codec hardwired in your code? Well, there are two cases. In the one case, the address is taken from the device tree, but in your case there appears to be no codec node so the hardcoded address is taken. johannes signature.asc Description: This is a digitally signed message part
Re: How can I get rid of the starting bong! (G4-mac mini)?
wrobell wrote: On Wed, 2006-03-29 at 15:39 +0200, Pancho Horrillo wrote: Hi! Mi G4 mac mini, following apple tradition, starts with a noisy bong!. [...] Speakerectomy apart, do you know any way to disable this bong? Any OpenFirmware variable that can be set? (I've looked for it, too, but no luck either). does nvsetvol 0 work for you? regards, wrobell [EMAIL PROTECTED] is there any way to change the bong chime for a customized sound like today is your best day?? ;-) thanks -- patoVala Linux User#280504 La poesía es un recuerdo de los mejores y más felices momentos de los mejores y más felices ingenios. -- Percy B. Shelley. (1792-1822) Poeta británico. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
On Wed, 2006-03-29 at 10:06 -0500, Patricio Valarezo wrote: is there any way to change the bong chime for a customized sound like today is your best day?? ;-) no. johannes signature.asc Description: This is a digitally signed message part
Re: snd-aoa on PowerMac 8,2
On Wed, 2006-03-29 at 16:57 +0200, Eduardo Trápani wrote: Is the address of the onyx codec hardwired in your code? I looked a bit into the apple stuff and the datasheet again -- it seems that both 0x46 and 0x47 are possible addresses. Can you try the latest code? johannes signature.asc Description: This is a digitally signed message part
Re: How can I get rid of the starting bong! (G4-mac mini)?
On Wed, Mar 29, 2006 at 03:45:30PM +0200, Johannes Berg wrote: On Wed, 2006-03-29 at 15:39 +0200, Pancho Horrillo wrote: Mi G4 mac mini, following apple tradition, starts with a noisy bong!. This is a real nuissance for me; I've talked to him, but to no avail... nvsetvol 0 It works! Danke. johannes -- Pancho Horrillo To be conscious that you are ignorant is a great step to knowledge. Benjamin Disraeli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
is there any way to change the bong chime for a customized sound like today is your best day?? ;-) no. Short of re-flashing OF, I guess :-) Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge installer for Mac Performa 6400/180 with 16MB RAM?
When we reboot the machine (after the initial stage of the woody installation) there's nothing in the screen and we have to recover using command + option + p + r. I guess We've been warned. What does *not* boot from OF mean? I'm sorry. I missed part of the thread and I just noticed it. I was not in debian-powerpc before. -- http://arhuaco.org/
Re: 2.6.16 kernel build errors
Eddy PetriXor wrote: On 3/29/06, Adam Done [EMAIL PROTECTED] wrote: I have been reading on the list of those who can't boot from their 2.6.16 kernel but I have not seen anyone else who are having build issues such as I. I have been trying and trying with many dif configurations and still come up with the same results. It looks like they are related to the errors other have been having with booting and sound issues. For my errors, they occur in the build process right after sound modules. snip INSTALL sound/core/oss/snd-mixer-oss.ko This is Debian, have you tried make-kpkg? Yes. This is what I have been using over the years... 1. make-kpkg clean #if a previous compile has been done 2. make xconfig 3. select kernel modules 4. make-kpkg --append-to-version [kernel version] kernel_image or make-kpkg --append-to-version [kernel version] -rev Custom.1 kernel_image 5. make-kpkg modules_image --append-to-version [kernel version] or make-kpkg modules_image --append-to-version [kernel version] -rev Custom.1 6. cd .. 7. dpkg -i kernel-image-[...] or Install kernel on destination box I have had a kernel in the past which would not finish building which ended up the same way and I just had to touch a file which the make process was not doing and it finished compiling but this time I tried that and the kernel did not even boot past yaboot in the initial screen showing the kernel name and before the actual kernel booting up. This is what I have done. # make-kpkg --append-to-version .ppc-pb1 -rev Custom.1 kernel_image or # make-kpkg --append-to-version .ppc-pb1 kernel_image This is using the vanilla kernel from kernel.org and using 'make oldconfig' from my last working kernel. I have even downloaded the kernel config from http://www.ppckernel.org/specialized.php and preformed a 'make oldconfig' from the powerbook config and I still get the same issue. Sadly, they all return the same results. The only conclusion I can come up with is that something is amiss in the vanilla kernel that is not agreeing with me. If there is a specific place to download the newest PPC kernel tree I don't know of yet? I have a standard box I compile all my Debian kernels which is a 800Hz G4 running Ubuntu and then the kernels are distributed out from there. -Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
On Wed, 29 Mar 2006 the mental interface of Pancho Horrillo told: Hi! Mi G4 mac mini, following apple tradition, starts with a noisy bong!. This is a real nuissance for me; I've talked to him, but to no avail... Hmm, the so called bong is a controlswitch for some harware issues as well, Some time ago I was wondering, why the is silent: There was one of the memory rows defekt on my pb. So I get nervous when I don't hear the fantastic bong ;) Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: snd-aoa on PowerMac 8,2
Is the address of the onyx codec hardwired in your code? I looked a bit into the apple stuff and the datasheet again -- it seems that both 0x46 and 0x47 are possible addresses. Can you try the latest code? I did, I get the same error. Tracing it a bit I noticed that still you are using port 0x47 (71). In aoa/codecs/onyx/snd-aoa-codec-onyx.h you have: #define ONYX_REG_DAC_OUTPHASE 71 I guess that should relate the base register somehow. Maybe something like ONYX_REG_BASE + 0 Then I could set my base register at 0x46 and the rest would work. Maybe. Eduardo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wanted: Debian Installer PowerPC porter(s)
On Wed, Mar 29, 2006 at 11:50:04AM +0100, Colin Watson wrote: On Wed, Mar 29, 2006 at 03:00:19AM +0200, Sven Luther wrote: - various old-world issues, including the work to free miboot, and inclusion of the free miboot version into the official archive. Mmm, i hope Colin Watson doesn't forget to add miboot support to his daily builds, or oldworld support will have been definitively killed. What do I need to do? (If at all possible, I'd prefer to produce a separate build for oldworld until such time as miboot is free, rather than having non-free material in the main daily build used on Debian CDs.) Oh, also this one : #355220: linux-kernel-di-powerpc-2.6: doesn't include tg3 modules, means Appple XServe G5 cannot netboot. Needs fixing, it is just adding the tg3 module to the di kernel modules, and reuploading. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i daily build fails when building initrd (PowerMac7,3)
On Mon, Mar 27, 2006 at 03:20:41PM +0200, Michael Schmitz wrote: Well, nice to hear it's not the hardware that's holding things up. Now we just need to find someone to volunteer to take over from you. Anyone? FWIW (I forget if the relevant thread was CCed here), I've volunteered, and the relevant bits of code have been switched over to look at my daily builds. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wanted: Debian Installer PowerPC porter(s)
Sven Luther [EMAIL PROTECTED] writes: #355220: linux-kernel-di-powerpc-2.6: doesn't include tg3 modules, means Appple XServe G5 cannot netboot. Needs fixing, it is just adding the tg3 module to the di kernel modules, and reuploading. tg3 has the firmware issue, no? -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
On 29 Mar, this message from Johannes Berg echoed through cyberspace: On Wed, 2006-03-29 at 15:39 +0200, Pancho Horrillo wrote: Mi G4 mac mini, following apple tradition, starts with a noisy bong!. This is a real nuissance for me; I've talked to him, but to no avail... nvsetvol 0 While this seems to work indeed, there is more to it, I beleive. Under OS X there are a few apps that can independantly of sound volume, change the volume of the startup sound. I have done this on mine, verified it is silent, but still nvsetvol shows a default volume of 24. So I believe there are two settings under OF, and I hope nvsetvol changes either both of them, or a master applzing to the two. Cheers Michel - Michel Lanners | Read Philosophy. Study Art. 23, Rue Paul Henkes|Ask Questions. Make Mistakes. L-1710 Luxembourg | email [EMAIL PROTECTED]| http://www.cpu.lu/~mlan| Learn Always. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How can I get rid of the starting bong! (G4-mac mini)?
On Wed, 2006-03-29 at 22:17 +0200, Mich Lanners wrote: Under OS X there are a few apps that can independantly of sound volume, change the volume of the startup sound. I have done this on mine, verified it is silent, but still nvsetvol shows a default volume of 24. and (at least on my powerbook) if I mute the master volume on OSX, there is no more BOING at startup. -- Yves-Alexis Perez -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wanted: Debian Installer PowerPC porter(s)
On Wed, Mar 29, 2006 at 05:11:05PM -0300, Otavio Salvador wrote: Sven Luther [EMAIL PROTECTED] writes: #355220: linux-kernel-di-powerpc-2.6: doesn't include tg3 modules, means Appple XServe G5 cannot netboot. Needs fixing, it is just adding the tg3 module to the di kernel modules, and reuploading. tg3 has the firmware issue, no? Sure, but it is currently shipped as part of the debian kernels, and as part of the x86 and other d-i kernel .udebs. For some obscure reason it was addeed on x86 and amd64 but not on powerpc. And then people wonder why i say that d-i kernel .udeb maintenance is a mess, and ask for neater technical solutions. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mounting
first i'm sorry if this has been asked but i just joined the list. I'm running the latest stable build of debian on a ppc G4 and am unable to write to any hfs+ drives. Altough I was able to and then it just stopped although mtab tells me it is mounted for rw i get the message that the drive is mounted read only when trying to write to it. I have looked all over the net and have seen mostly old messages about this being a problem in the past. but nothing pointing to it being an issue now. I also tried hpmount and it tells me it is not a mac drive. This may be because it is not my main volume or because i turned journaling off. Im not sure. Any help would rock Caleb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: snd-aoa: new apple sound driver
On Wed, 2006-03-29 at 15:00 +0200, Johannes Berg wrote: On Wed, 2006-03-29 at 15:01 +1100, Benjamin Herrenschmidt wrote: BTW.. with the current stuff, if I install the modules and then do modprobe i2sbus I get a registration error in dmesg. Hmm. What's the error? Can't reproduce this at all. Also, what machine? It works fine on my powermac, even when i2sbus is auto-loaded due to binding to the macio i2s device alias. On the laptop. Mar 29 11:11:51 localhost kernel: [ 192.069735] i2sbus: found i2s controller Mar 29 11:11:51 localhost kernel: [ 192.069752] soundbus: adding device failed sanity check! Mar 29 11:11:51 localhost kernel: [ 192.069757] i2sbus: device registration error! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: snd-aoa: new apple sound driver
Note sure what you mean here... I'll come back with a better explanation later :) I want first to have a look at the most recent code and think a bit more :) Then, the core would get events from interrupts (or clock switches from the codecs) via a yet-to-be-defined call and would react by calling the various mute/unmutes accordingly for available inputs and outputs on the bus where the event occured. Ah but you see, the codec actually mutes the digital output when it isn't usable, and the codec also mutes the analog output when we transfer compressed data. We don't amp-mute in that case, but just from the codec, so no analog audio is even leaving the codec. Yes, but we should probably still mute the amps... especially when using a separate analog codec (like tas3004 + topaz setups). For things like headphone/speaker automute, I think we need a kind of tristate.. either that, or we need a bit mask of mute conditions. When any of them is set, it's muted. That way, the user mute control sticks regardless of the automute action or temporary mute to analog outputs because, for example, the digital input lost its clock and we are switching (we need to mute to avoid clics). Yeah. I have to think a bit about an in-snd-aoa api for all this. I was thinking about an event based mecanism... snd-aoa has an array of all inputs outputs, which codec handles them, and, if relevant, handles to connector detect GPIOs and amp mute GPIOs. Then it has an event notification callback that's called in by the codec and the GPIO interrupts as a result of state changes, clock changes etc... From these, snd-aoa can do the right thing, do mutes, unmutes, etc.. when needed. Hrm... So my feature calls are doing too much at once... (they both do the clocks and the cell enable). I don't do clock refcounting like Apple does tho, thus the main clock sources are always enabled. So I think all you have to do is toggle the I2Sn_CLK_ENABLE bits ... Hmm. How do I get at those bits? Clock refcounting would be nice too, along with proper power save management... Clock refcounting will be done ... some other time :) Can you verify if all machines that have digital inputs (thus all machines for which you may need to do that kind of clock switching) also have working platform functions for doing so ? If they do, then it's really just a matter of calling those. If not, then we can either ioremap the FCR's in the driver and play with them (evil solution + possibly locking problems) or add a feature call. The former isn't feasible since I need to do clock switching even on analog-only machines to support more sample rates than the 44.1 KHz that the firmware sets for the boing sound :) And you need to turn the clock off for that ? All the FCRs are useful for you is to turn the clock input on and off, you shouldn't need that except when switching to an external clock no ? And even then ... AFAIK, Darwin AppleOnBoardAudio isn't playing with those FCRs at all unless I've missed something, all it does is to call in PowerI2S via platform calls to AppleKeyLargo which is equivalent to the existing pmac feature call... I need to understand better what you are exactly trying to do here and what FCR bits you want to toggle and when. In any case, if you look at arch/powerpc/platforms/powermac/feature.c, You can see how FCRs are manipulated. The macros MACIO_IN/OUT read/write from FCRs and MACIO_BIC/BIS clear/set bits. LOCK/UNLOCK are used to protect (it's just a spinlock). Look specifically at g5_i2s_enable() for K2/shasta based machines. There is also core99_sound_chip_enable() for Keylargo based machines (32 bits machines) though the current version does nothing to the i2s bus, it just toggles a GPIO known to control power to the codec on some machines. That is, it assumes that i2s is enabled and clocked at boot. The sleep code in there does switch it off on sleep and back on though but that's a different thing. In the later case, you add a feature call in pmac_feature.h and the appropriate entry in the table in feature.c and then you can toggle bits as you wish with appropriate locking (look at eixsting code in there). I can give you more details on irc if you need. Ok. I definitely need more details I think. But it would be nice if it could all be done with platform functions instead. Hardly possible though, see above. Well, again, I have to understand better why here ...You shouldn't need to touch the FCRs for normal frequency changes unless I missed something. Modalias situtation. I played some tricks: i2sbus depends on soundbus Yeah :) There might be some issue with the macio automatching from userland, not sure yet, could just be missing bits in hotplug scripts. macio automatching is working, i2sbus loads, but the latter modules don't. I guess there's a userland issue in that it doesn't pick up new devices that are added to /sys while it is
Re: mounting
On Wed, 2006-03-29 at 17:40 -0500, caleb storms wrote: first i'm sorry if this has been asked but i just joined the list. I'm running the latest stable build of debian on a ppc G4 and am unable to write to any hfs+ drives. Altough I was able to and then it just stopped although mtab tells me it is mounted for rw i get the message that the drive is mounted read only when trying to write to it. I have looked all over the net and have seen mostly old messages about this being a problem in the past. but nothing pointing to it being an issue now. I also tried hpmount and it tells me it is not a mac drive. This may be because it is not my main volume or because i turned journaling off. Im not sure. Any help would rock You probably have a dirty drive (crashed without unmounting it). This requires running fsck. I don't know if there's a working hfs+ fsck for linux, in the meantime, a fix is to boot OS X and back into linux. (You can also verify/repair the partition by booting with the OS X install CD and going to the disk utilities). Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
