> Just wondering if anyone has found time to look into fixing the input
> quality of the usb quattro?
>
> I'm not sure it has ever functioned perfectly for input quality.
>
> Currently I get a better sound quality from my $10 cmipci than my $400
>
> usb-quattro ;-P
>
> There is a constant crac
hi all,
both ico and myself were able to solve our problems with the hdsp and
the cardbus interface:
ene1410 cardbus bridge (ico):
ico had to enable "Memory read burst enable upstream" and "TLTEnable" on
his cardbus bridge. the fix for that was added to the kernel's pcmcia
subsystem and is proba
hi russell and others ...
i'm curious, since our discussion got quiet in the last few days ... if
ico was able to solve his problem by altering cardbus registers, but my
hdsp works fine with windows with the same register settings on the
cardbus bridge that won't work with linux ... what does this
hi all,
i installed windows to check if there is anything happening to the
cardbus registers when working on a supported system... the cardbus
registers, beside the pci registers, are the same as on the linux system
...
i haven't been able to play back some sounds, because rme's driver disc
only
> Only the first 0x48 registers are defined by the base specification;
> the rest are chip and/or manufacturer specific.
i see ...
> The registers which Ico is changing are specific to the ENE CB1410,
> which are a clone of the TI chips.
>
> Your cardbus bridge isn't a clone of TI, so I wouldn't
hi ico, hi russell
first of all, congratulations that you, ico, got your hdsp working ...
anyway the registers you were changing have no effect on my setup ... they are zero:
your configuration:
> [EMAIL PROTECTED] 00]# hexdump
> -v /proc/bus/pci/00/0a.0
> 000 1524 1410 0007 0210 0607
hi all,
> > 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
>
> $ setpci -s a.0 0xc9.b
>
> will display the value of this register under Linux, and:
>
> $ setpci -s a.0 0xc9.b=value
i trie
> It's called "System Explorer v.1.00"
> Screenshot of the pcmcia controller's state while card is
> disconnected:
> http://meowing.ccm.uc.edu/~ico/eMachines/SE-before_suspend.jpg
> Written by Danny Liu (AMI) and it's free (supposedly, haven't looked
> for it on the Internet just yet, too tired rig
> 2) The Windows driver automatically adjusts any pcmcia controller's
> latency from (in my case default, yours could vary) 0x20 (or 32) to
> 0xFF (or 255). This always happens except in one case where the card
> remains plugged-in during the suspend/resume cycle which Matthias
> acknowledged it ma
> agreed. but its much more likely to be something about the cardbus
> support under linux than the hdsp driver, and neither side (the
> cardbus people or us hdsp people) knows the other side at all.
to figure that out, someone who knows what's going on in the hdsp driver
has to tell the pcmcia guy
On Sun, 04 Apr 2004 10:53:28 -0400
Paul Davis <[EMAIL PROTECTED]> wrote:
> >mainly the alsa guys who wrote the driver and know, how they access
> >the bus system and the hardware, have to tell the pcmcia guys, who
> >know, what's going on in the bus ... i CC'd this mail to the thomas
> >charbonnel
hi ico,
you did a good job in documenting this problem ...
> TODO:
> 1) Log the Jack -R output (likely to be ridden with xrun's)
i suppose, we will get the same result as me, with jack complaining
about latency problems...
> 2) You tell me :-)
i suppose, what we are able to do, has been done ..
hi russel
> The majority of PCMCIA is the same between the two kernels. There
> have been some cleanups and changes to the way card events (insertions
> and removals) occur, and some setup changes to the cardbus bridge to
> turn on some extra features.
>
> However, if you're saying that 2.4 and
> What needs to happen is that the card driver author needs to
> investigate what is going on, and, if it seems related to the core
> PCMCIA core or the socket driver, we need to get involved.
he pointed out that it's probably a kernel problem ...
we don't want you to solve problems of the alsa dr
> 1) provide detailed lspci
would it be possible, that you send be your lspci -v output?
this is mine:
bash-2.05b# lspci -v
:00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host
Bridge (rev 04)Subsystem: Acer Incorporated [ALI]: Unknown
device 0019Flags: bus mast
hi all,
> NOTE: I am cc-ing this to the kernel list in hope someone there might
> have a better insight in this. For the kernel people who intend to
> respond to this, I would greatly appreciate it if you could CC me, as
> I am not subscribed to the kernel list.
i'm following ico's policy in this
> My guess is that the problem is the pcmcia bus is somehow 2000 times
> slower than it should be.. csound seems to confirm this hypothesis
> from the command line when attempting realtime synthesis:
i seem to know this problem ...
first of all, which cardbus bridge do you have? (lspci -v)
here
On Sat, 20 Mar 2004 00:35:02 -0500
"Ivica Ico Bukvic" <[EMAIL PROTECTED]> wrote:
> First off I would like to extend my sincere apologies for my atrocious
> cross-posting. I am currently in a rather desperate situation and
> would highly appreciate any help I can get in this matter.
>
> e
wait ..
> Am Mittwoch, 3. März 2004 20:17 schrieb Tim Blechmann:
> > are you planing to use this machine with a hdsp?
>
> I'm afraid not, but I'd kindly test it for you if you sent me a hdsp
> (cardbus iface, this is a laptop).
would it be possible that you send me the ls
> has anyone on this list ALSA, JACK or RME's hdsp running on an AMD 64?
> Are there any problems known about the x86 "port" regarding audio?
i don't have anythink like that running, but i consider getting an amd64
notebook for the same setup myself ...
do you know, how the floating point performa
hi all,
i tried to run the hammerfall dsp using the pcmcia-cs driver for the
yenta-socket instead of the kernel driver and the behaviour of the card
is the same ...
so, do you have any insights, what's the difference between both
drivers, or what is the same? is there anything, that could cause s
hi all,
this is my first posting to the kernel list, that's why i don't know, if
i'm right here ... if not, please drop me a line and tell me who i
should ask...
i'm experiencing problems with the O2 micro 6933 card when trying to use
the hammerfall dsp sound device. i'm using the yenta socket dr
> Could people experiencing problems with their hdsp (namely Tim and
> Paul) try the attached patch ?
i tried the patch you sent me ... no success ... i tried to play a
soundfile with aplay using different period-sizes ...
the file always had the same distortions ...
btw, the patch just changed the
hi all,
i just got an email from someone who experienced a problem similar to
mine:
> It sounds just like the problem I had. I even sent my laptop and card
> to Paul for toubleshooting. It turned out to be a problem with the
> firmware version. The card I had used a newer version.
i heard that yo
> Maybe someone can help with configure options or anything to get the
> module compiled (the snd-hammerfall_mem.c file is there but the .o
> file is missing) if it is needed or what else to do to get the rme
> working.
afaik the memory allocation for the hdsp moved from snd-hammerfall-mem
to snd-p
> Paul Davis experienced this recently with his cardbus/digiface,
> with both 0.9.8 and 1.0.x. He found that it only does this when
> the period size is >= 512. At 256 and below, it works fine for
> him. Give that a try...
it's not working on my system (i tried 64, 128, 256) ... but playing
i've got a problem with my hammerfall dsp (multiface + cardbus) ...
it might be an alsa problem: i can load all modules and upload the
firmware with hdsploader ... and i can mix the inchannels to the
outchannels with hdspmixer ...
but when i start a sound application (jack,oss layer, aplay) every
Hi all,
i already posted this problem at the alsa-user list, but it seems that
no one experienced this problem.
i've got some problems with my maudio quattro. i'm using the .asoundrc
file from alsa-project.org to use all 4 channels. (file is attached)
it worked fine with alsa up to 0.9.2.
but wit
28 matches
Mail list logo
