public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ivica Ico Bukvic" <ico@fuse.net>
To: <daniel.ritz@gmx.ch>
Cc: "'A list for linux audio users'" 
	<linux-audio-user@music.columbia.edu>,
	"'Russell King'" <rmk+lkml@arm.linux.org.uk>,
	<alsa-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>,
	<linux-pcmcia@lists.infradead.org>,
	"'Thomas Charbonnel'" <thomas@undata.org>, <ccheney@debian.org>,
	"'Tim Blechmann'" <TimBlechmann@gmx.net>
Subject: RE: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news
Date: Fri, 9 Apr 2004 23:30:31 -0400	[thread overview]
Message-ID: <20040410033032.XOVD8029.smtp1.fuse.net@64BitBadass> (raw)
In-Reply-To: <200404100347.56786.daniel.ritz@gmx.ch>

Thank you very much for an exhaustive breakdown of this issue! Your
assistance has been truly helpful!

I am aware that this burst stuff should be enabled on the 2.6 kernel,
however I am still getting bad results.

The 06 to 04 may be the critical element as even when I have everything
properly running in Win32, when I alter this number the distortion returns
(it is almost like an azimuth on old analogue tape decks that one would
adjust using screwdriver in order to successfully load a program into a
Commodore64 or the legendary Sinclair ZX Spectrum :-).

If I do figure out the problem in Linux and find out that a particular
register is the issue, how can I make my linux box adjust this register at
boot-time (a simple hack-like script in a form of a service comes to mind
but I was hoping to perhaps see a more universal solution if possible)?

Best wishes,

Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico/
 
> -----Original Message-----
> From: Daniel Ritz [mailto:daniel.ritz@gmx.ch]
> Sent: Friday, April 09, 2004 9:48 PM
> To: Ivica Ico Bukvic
> Cc: linux-kernel
> Subject: RE: [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion
> -- First good news
> 
> you can get the same output with
> 	hexdump -v /proc/bus/pci/BUS/DEVICE
> where BUS/DEVICE is the CB controller. eg. 00/09.0
> 
> about the bits:
> - at 81h, from D0 to 90: this is part of the system control register. the
> bit
>   that changed is "Memory read burst enable upstream"
> - at c9h, from 04 to 06: this is an undocumented test register. TI just
> says
>   reserved, EnE says test register, for the bit that changed it adds the
>   comment TLTEnable (default to 1). no idea what it is. it _could_ have
>   something to do with the cardbus latency timer...you can try to play a
> bit
>   with the latency setting after resume when this bit is set. try writing
> to
>   offset 1Bh, put in at least 40h
> 
> to change the bits under linux, use setpci (also good for reading)
> 
> about the memory read burst upstream: 2.6 kernels enable it for most of
> the TI chips and since 2.6.5 also for some TI clones from EnE (incl.
> EnE1410).
> 
> rgds
> -daniel




  reply	other threads:[~2004-04-10  3:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-10  1:47 [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- First good news Daniel Ritz
2004-04-10  3:30 ` Ivica Ico Bukvic [this message]
2004-04-11 13:25   ` Russell King
2004-04-11 16:08     ` Tim Blechmann
2004-04-11 23:45       ` Daniel Ritz
2004-04-12  1:39         ` [linux-audio-user] snd-hdsp+cardbus+M6807 notebook=distortion -- FIXED! Ivica Ico Bukvic
2004-04-12  7:28           ` Russell King
2004-04-12  9:08             ` David Hinds
2004-04-12  9:27               ` Russell King
2004-04-12 14:40             ` Ivica Ico Bukvic
2004-04-12 14:53               ` Russell King
2004-04-12 15:31                 ` Daniel Ritz
2004-04-12 15:38                   ` Russell King
2004-04-12 18:03                     ` Daniel Ritz
2004-04-14 13:41                     ` Tim Blechmann
2004-04-12 22:06               ` Tim Blechmann
2004-04-12 11:02           ` Tim Blechmann
2004-04-12 10:39             ` Russell King
2004-04-12 12:09               ` Tim Blechmann
2004-04-12 15:19           ` Daniel Ritz

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=20040410033032.XOVD8029.smtp1.fuse.net@64BitBadass \
    --to=ico@fuse.net \
    --cc=TimBlechmann@gmx.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ccheney@debian.org \
    --cc=daniel.ritz@gmx.ch \
    --cc=linux-audio-user@music.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=thomas@undata.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