* [ALSA - driver 0001697]: Sound does not work
@ 2006-01-01 9:27 bugtrack
0 siblings, 0 replies; 4+ messages in thread
From: bugtrack @ 2006-01-01 9:27 UTC (permalink / raw)
To: alsa-devel
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1697>
======================================================================
Reported By: rkoenig
Assigned To: sashak
======================================================================
Project: ALSA - driver
Issue ID: 1697
Category: PCI - intel8x0m
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: doesn't matter
Kernel Version: doesn't matter
======================================================================
Date Submitted: 01-01-2006 10:27 CET
Last Modified: 01-01-2006 10:27 CET
======================================================================
Summary: Sound does not work
Description:
The SiS 7012 based sound controllers on all the mainboards of Fujitsu
Siemens Computers refuse to work.
The reason is that the hardware setup is done in a way so that the codec
is the tertiary codec. Problem is that during initialisation the
snd_intel8x0 driver checks the ready bit for the tertiary codec on bit 28
of the global status register, but on SiS 7012 the codec ready status is
set in bit 18. But even fixing that in source doesn't help much because
the driver has to many branches that are depending on the chip type
(INTEL, SIS, whatever) so that I get a codec ready, but then subsequent
errors from the codecs.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
01-01-06 10:27 rkoenig New Issue
01-01-06 10:27 rkoenig Distribution => doesn't matter
01-01-06 10:27 rkoenig Kernel Version => doesn't matter
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ALSA - driver 0001697]: Sound does not work
@ 2006-01-07 0:26 bugtrack
0 siblings, 0 replies; 4+ messages in thread
From: bugtrack @ 2006-01-07 0:26 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1697>
======================================================================
Reported By: rkoenig
Assigned To: sashak
======================================================================
Project: ALSA - driver
Issue ID: 1697
Category: PCI - intel8x0m
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: doesn't matter
Kernel Version: doesn't matter
======================================================================
Date Submitted: 01-01-2006 10:27 CET
Last Modified: 01-07-2006 01:26 CET
======================================================================
Summary: Sound does not work
Description:
The SiS 7012 based sound controllers on all the mainboards of Fujitsu
Siemens Computers refuse to work.
The reason is that the hardware setup is done in a way so that the codec
is the tertiary codec. Problem is that during initialisation the
snd_intel8x0 driver checks the ready bit for the tertiary codec on bit 28
of the global status register, but on SiS 7012 the codec ready status is
set in bit 18. But even fixing that in source doesn't help much because
the driver has to many branches that are depending on the chip type
(INTEL, SIS, whatever) so that I get a codec ready, but then subsequent
errors from the codecs.
======================================================================
----------------------------------------------------------------------
sashak - 01-07-06 01:26
----------------------------------------------------------------------
You are about sound (intel8x0) and not modem (intel8x0m) driver? (This
report was opened for intel8x0m - modem driver).
About the problem itself. Is this general feature(s) of SiS7012 or
something specific for FS machines (AFAIK SiS7012 data sheet is not
published)? Which errors do you have after ICH_TCR redefine?
And about driver split I think it is not needed just because different
ICH_TCR values - this may be solved in current driver. And anyway I don't
have reference hardware.
Issue History
Date Modified Username Field Change
======================================================================
01-01-06 10:27 rkoenig New Issue
01-01-06 10:27 rkoenig Distribution => doesn't matter
01-01-06 10:27 rkoenig Kernel Version => doesn't matter
01-07-06 01:26 sashak Note Added: 0007500
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ALSA - driver 0001697]: Sound does not work
@ 2006-01-07 20:07 bugtrack
0 siblings, 0 replies; 4+ messages in thread
From: bugtrack @ 2006-01-07 20:07 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1697>
======================================================================
Reported By: rkoenig
Assigned To: sashak
======================================================================
Project: ALSA - driver
Issue ID: 1697
Category: PCI - intel8x0m
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: doesn't matter
Kernel Version: doesn't matter
======================================================================
Date Submitted: 01-01-2006 10:27 CET
Last Modified: 01-07-2006 21:07 CET
======================================================================
Summary: Sound does not work
Description:
The SiS 7012 based sound controllers on all the mainboards of Fujitsu
Siemens Computers refuse to work.
The reason is that the hardware setup is done in a way so that the codec
is the tertiary codec. Problem is that during initialisation the
snd_intel8x0 driver checks the ready bit for the tertiary codec on bit 28
of the global status register, but on SiS 7012 the codec ready status is
set in bit 18. But even fixing that in source doesn't help much because
the driver has to many branches that are depending on the chip type
(INTEL, SIS, whatever) so that I get a codec ready, but then subsequent
errors from the codecs.
======================================================================
----------------------------------------------------------------------
sashak - 01-07-06 01:26
----------------------------------------------------------------------
You are about sound (intel8x0) and not modem (intel8x0m) driver? (This
report was opened for intel8x0m - modem driver).
About the problem itself. Is this general feature(s) of SiS7012 or
something specific for FS machines (AFAIK SiS7012 data sheet is not
published)? Which errors do you have after ICH_TCR redefine?
And about driver split I think it is not needed just because different
ICH_TCR values - this may be solved in current driver. And anyway I don't
have reference hardware.
----------------------------------------------------------------------
rkoenig - 01-07-06 21:07
----------------------------------------------------------------------
Hi there,
yes, you're right this one should be for intel8x0 (damn, looks like I need
better glasses :-) ).
The issue is general for all 7012 hardware. The boards from other vendors
that I have ssen so far are using the primary codec, so they don't suffer
from the error. FSC is using the teriary codec and the driver is messing
up.
Since I'm not at the office at the moment I can't tell you the exact
errors, but for me it looks like that intex8x0 tries to talk to the codec
and the codec doesn't answer (returncode 0xffffff). On monday I can try it
out and see the details about that.
About the split: Seeing the source code of intel8x0 its what we in Germany
call "eierlegende Wollmilchsau" (a pig that producess eggs, wool and
milk), its a driver that is covering so many chips that a big amount of
code is just to check what chipset is used. So there are a thousand
possible branches and I'm afraid that this makes the code difficult to
maintain. And its not just the ICH_TCR issue. Reading the SIS spec I see
other things like e.g. warm reset that needs a special treatment on SiS,
but nothng like that is done.
I'm aware of the lack of public documentation so at the moment one of our
actions is to urge SiS to release the programming guide without NDA. I
know that the driver is very good for a driver written without spec, but
it could be much better if a spec would be available. I hope that we have
some progress in that issue, so far it looked like all people at SiS are
on holidays.
As far as the hardware is concerned, that shouldn't be a problem. I have a
budget and I can donate hardware to developers if they help us improving
the drivers. We already did this approach for SATA drivers (also for SiS)
and that was a very successful action.
So if we get the permission from SiS to distribute the spec and some of
you guys is willing to hack the driver then we should talk soon about the
proceedings.
Issue History
Date Modified Username Field Change
======================================================================
01-01-06 10:27 rkoenig New Issue
01-01-06 10:27 rkoenig Distribution => doesn't matter
01-01-06 10:27 rkoenig Kernel Version => doesn't matter
01-07-06 01:26 sashak Note Added: 0007500
01-07-06 21:07 rkoenig Note Added: 0007520
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 4+ messages in thread
* [ALSA - driver 0001697]: Sound does not work
@ 2006-01-10 15:49 bugtrack
0 siblings, 0 replies; 4+ messages in thread
From: bugtrack @ 2006-01-10 15:49 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1697>
======================================================================
Reported By: rkoenig
Assigned To: sashak
======================================================================
Project: ALSA - driver
Issue ID: 1697
Category: PCI - intel8x0m
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: doesn't matter
Kernel Version: doesn't matter
======================================================================
Date Submitted: 01-01-2006 10:27 CET
Last Modified: 01-10-2006 16:49 CET
======================================================================
Summary: Sound does not work
Description:
The SiS 7012 based sound controllers on all the mainboards of Fujitsu
Siemens Computers refuse to work.
The reason is that the hardware setup is done in a way so that the codec
is the tertiary codec. Problem is that during initialisation the
snd_intel8x0 driver checks the ready bit for the tertiary codec on bit 28
of the global status register, but on SiS 7012 the codec ready status is
set in bit 18. But even fixing that in source doesn't help much because
the driver has to many branches that are depending on the chip type
(INTEL, SIS, whatever) so that I get a codec ready, but then subsequent
errors from the codecs.
======================================================================
----------------------------------------------------------------------
rkoenig - 01-07-06 21:07
----------------------------------------------------------------------
Hi there,
yes, you're right this one should be for intel8x0 (damn, looks like I need
better glasses :-) ).
The issue is general for all 7012 hardware. The boards from other vendors
that I have ssen so far are using the primary codec, so they don't suffer
from the error. FSC is using the teriary codec and the driver is messing
up.
Since I'm not at the office at the moment I can't tell you the exact
errors, but for me it looks like that intex8x0 tries to talk to the codec
and the codec doesn't answer (returncode 0xffffff). On monday I can try it
out and see the details about that.
About the split: Seeing the source code of intel8x0 its what we in Germany
call "eierlegende Wollmilchsau" (a pig that producess eggs, wool and
milk), its a driver that is covering so many chips that a big amount of
code is just to check what chipset is used. So there are a thousand
possible branches and I'm afraid that this makes the code difficult to
maintain. And its not just the ICH_TCR issue. Reading the SIS spec I see
other things like e.g. warm reset that needs a special treatment on SiS,
but nothng like that is done.
I'm aware of the lack of public documentation so at the moment one of our
actions is to urge SiS to release the programming guide without NDA. I
know that the driver is very good for a driver written without spec, but
it could be much better if a spec would be available. I hope that we have
some progress in that issue, so far it looked like all people at SiS are
on holidays.
As far as the hardware is concerned, that shouldn't be a problem. I have a
budget and I can donate hardware to developers if they help us improving
the drivers. We already did this approach for SATA drivers (also for SiS)
and that was a very successful action.
So if we get the permission from SiS to distribute the spec and some of
you guys is willing to hack the driver then we should talk soon about the
proceedings.
----------------------------------------------------------------------
sashak - 01-10-06 16:49
----------------------------------------------------------------------
SiS 7012 spec public release and hardware donation are very good ideas.
Thanks.
So as far as I can understand the problem is specific for FSC machines
because of teriary codec. And what about modem (sometimes it is called
SiS7013)?
We have a problem with Conexant's AC97 modems support. Basically I am
modem (intel8x0m) maintainer, and interesting in solving modem problems
(of course I may look for sound related things first).
Issue History
Date Modified Username Field Change
======================================================================
01-01-06 10:27 rkoenig New Issue
01-01-06 10:27 rkoenig Distribution => doesn't matter
01-01-06 10:27 rkoenig Kernel Version => doesn't matter
01-07-06 01:26 sashak Note Added: 0007500
01-07-06 21:07 rkoenig Note Added: 0007520
01-10-06 16:49 sashak Note Added: 0007551
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-01-10 15:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-07 0:26 [ALSA - driver 0001697]: Sound does not work bugtrack
-- strict thread matches above, loose matches on Subject: below --
2006-01-10 15:49 bugtrack
2006-01-07 20:07 bugtrack
2006-01-01 9:27 bugtrack
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox