On 9 Jun, Paul Tomlin wrote:
> I have a similar spec machine (SS20, dual SS50 cpu) to the one you
> are having problems with. If you want to send some code over, and
> some detailed instructions on how to test it, I'll happily try it
> out this end.
On 9 Jun, J. S. Connell wrote:
> Not being a SPARC kernel hacker, all I can offer is my dual-CPU SS10 for
> testing. I have a SpeakerBox I'd love to get some noise out of...
I just pushed the current version of the code up to vger, on the
default (2.3) branch. The code is contained in the directory
drivers/sbus/audio/ The files are dbri.[ch] and cs4215.h
If you compile DBRI as a module, you can control the debugging at
modprobe time using the variable dbri_debug. For example,
modprobe dbri dbri_debug=4
and
modprobe dbri dbri_debug=5
give me dramatically different results on my SS20. "4" causes the
command buffer to be printed before its sent to the DBRI, and the extra
"1" provides just enough more printk to make the thing actually work.
It's the first command buffer that's the problem; i.e, with
dbri_debug=5 (working), I get:
Jun 9 22:47:12 vyger kernel: DBRI: Found SUNW,DBRIe in SBUS slot 4
Jun 9 22:47:12 vyger kernel: DBRI: DMA Cmd Block 0xfff27000 (0xfff27000)
Jun 9 22:47:12 vyger kernel: DBRI: reset 0:4008 2:9 8:0 9:0
Jun 9 22:47:12 vyger kernel: DBRI: init: cmd: fff27000, int: fff27100
Jun 9 22:47:12 vyger kernel: DBRI cmd: fff27000:38000000
Jun 9 22:47:12 vyger kernel: DBRI cmd: fff27004:fff27100
and then a bunch more stuff, but with dbri_debug=4 (broken; no printks
for the first four lines) I get:
Jun 9 22:47:03 vyger kernel: DBRI cmd: fff26000:38000000
Jun 9 22:47:03 vyger kernel: DBRI cmd: fff26004:00000000
Jun 9 22:47:03 vyger kernel: DBRI: Chip never acked WAIT
Notice the difference in the command buffer. (The second column of
values; the first column is the address). I'm at a loss to explain it.
Please let me know if you can duplicate these results.
[EMAIL PROTECTED] wrote:
> hmm... since when did the the SS20 have external ISDN connection?
> it has the DBRI chip for audio but the ISDN port is somehow disabled.....
The SS20 doesn't have ISDN (it works fine, but there's no wiring for
the port). The driver can't tell the difference (it doesn't know
what's wired to the chip) and doesn't care.
> on the SS20 or the LX?
The problem occurs on the SS20; the LX works fine no matter what
settings I use.
--
-bwb
Brent Baccala
[EMAIL PROTECTED]
-------------------------------------------------------------------------
To receive periodic news about what's happening at freesoft.org, send
email to "[EMAIL PROTECTED]", with "SUBSCRIBE" as the message, i.e:
echo SUBSCRIBE | mail [EMAIL PROTECTED]
-------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
