Posted by
chrisd
on from the it's-water-helen-water dept.
davster writes "I was just checking out the Linux 2.5changeset and noticed that Linus has just merged ALSA into his tree. Its about time."CD: Looks like Jaroslav Kysela did the merge work, but Linus obviously allowed it to happen. I'm a happy Alsa user so this looks like a good thing.
Re:To anyone who is wondering: this is a Big Deal
by
Anonymous Coward
·
· Score: -1, Troll
Quite frankly, for the average person, ALSA stinks. It is a big nasty mess.
ALSA in any distro default kernels?
by
mlinksva
·
· Score: 2, Troll
Si, no, plans? Anyone know? I hope they don't all wait for 2.6.
Anyone ever notice how much Linux is posted?
by
amhax
·
· Score: -1, Troll
VA Systems is no longer VA Linux systems. Shouldn't slashdot be posting a wider variety of things now instead of just mindless Linux drivel? I keep submitting BSD news and other such things, but they keep getting rejected. Odd...
You know what? NO ONE CARES. Linux is a gigantic piece of SLOP. It's like a LOG OF DOGSHIT floating in cat urine. A stinking LOG OF DOGSHIT covered in maggots floating in cat urine. It crashes. It OOPSES. It locks up, it hangs, it randomly corrupts my FUCKING filesystem. I'd rather have my TESTICLES TORN OFF with a hot pair of serrated pliers than run Linux on my FUCKING computer again! It's an absolute pile of SLOP dribbled out of LINUS TURDBALLS's and ANAL COX's cocks during one of their HOMOSEXUAL FAGGOT ORGIES.
BIG MISTAKE!
by
Anonymous Coward
·
· Score: -1, Troll
I completely disagree. I have looked at and worked on the codebase, it does not rock. It doesnt take into consideration may point of contention and system lock up. Linus really needs to regulate this code much better! The developer of this code has a major fundamental lack of understanding when it comes to kernel objects and maintaing prioritization levels and queuing and defferment of interrupt handling.
This will come back to haunt the kernel. You have been warned.
Re:BIG MISTAKE!
by
Anonymous Coward
·
· Score: -1, Troll
Well, Paul, you happen to be wrong. I am neither or troll and I do know what I am talking about. If you would just care to re-read my post and apply it to the situations that are clearly overlooked in the code you will understand. As far as you go you constantly respond to posters who have extensive knowledge with nothing but beratement. You have a reputation here that is earned only by the unknowing/uneducated slashdot moderators.
As far as deferrment of interrupts being low level driver responsibility - duh! That is the point.
Any good kernel hacker would be able to see that the code is a priority inversion lock waiting to happen. Just wait for it to surface now since the users have it in hand.....
Enjoy the debugging....
Re:BIG MISTAKE!
by
Anonymous Coward
·
· Score: -1, Troll
ALSA sucks the big one. After downloading and very carefully following the
build instructions (CMI 8738 chipset), I
fire it up and it dumps core. Hmmm. Ahh yes,
a couple of years ago I tried ALSA with my
Yamaha chip, it dumped core then too. Try another
version. Dumps core. Try an older version. Dumps
core. Try a bleeding edge version. Dumps core.
Someone in another thread pointed out that
ALSA is like WINE - it works on the developers
machines and in the mailing list chit-chat, but
for real users it is a cluster fuck.
Re:BIG MISTAKE!
by
Anonymous Coward
·
· Score: -1, Troll
LOL! Yup you caught me, it was a complete troll, as i made it all up...
I do, however, findy you absurdly condescending. And, BTW, your online resume sucks balls.
So, um... Is Crystal SoundFusion CS4624 support working yet?
I have a Hercules Gamesurround Fortissimo II (replaced my AWE64). It wasn't clear if the OSS modules included with kernel 2.2.19 supported it, so I decided to give ALSA a try. I downloaded and installed ALSA 0.5 some time ago. While the modules detected my card and configured themselves just fine, I got no sound out of the speakers. (Yes, I used alsamixer to turn up the volume on the appropriate channels.)
Someone on the alsa-user mailing list suggested it might have something to do with the "power management" on the newer chip, and to try ALSA 0.9.something (alpha-ware), which has code to handle it. So I did. It compiled, installed, detected my card, and configured itself just fine. alsamixer opens and lets me fool with sliders without trouble. Even the OSS compatibility modules come up fine. But I still can't hear anything.
I haven't touched it since then, as I've been consumed by other distractions. Clearly I'm doing something wrong. But I'm at a complete loss as to what it might be.
Re:What's going on with Linus?
by
Anonymous Coward
·
· Score: -1, Troll
Yes, Linus has held back the state of Linux and
also the state of computing by more than 10 years.
Sadly, in their attempt to identify with and
deify Linux, people just don't realize this.
Quite frankly, for the average person, ALSA stinks. It is a big nasty mess.
Si, no, plans? Anyone know? I hope they don't all wait for 2.6.
VA Systems is no longer VA Linux systems. Shouldn't slashdot be posting a wider variety of things now instead of just mindless Linux drivel? I keep submitting BSD news and other such things, but they keep getting rejected. Odd...
You know what? NO ONE CARES. Linux is a gigantic piece of SLOP. It's like a LOG OF DOGSHIT floating in cat urine. A stinking LOG OF DOGSHIT covered in maggots floating in cat urine. It crashes. It OOPSES. It locks up, it hangs, it randomly corrupts my FUCKING filesystem. I'd rather have my TESTICLES TORN OFF with a hot pair of serrated pliers than run Linux on my FUCKING computer again! It's an absolute pile of SLOP dribbled out of LINUS TURDBALLS's and ANAL COX's cocks during one of their HOMOSEXUAL FAGGOT ORGIES.
I completely disagree. I have looked at and worked on the codebase, it does not rock. It doesnt take into consideration may point of contention and system lock up. Linus really needs to regulate this code much better! The developer of this code has a major fundamental lack of understanding when it comes to kernel objects and maintaing prioritization levels and queuing and defferment of interrupt handling.
This will come back to haunt the kernel. You have been warned.
So, um... Is Crystal SoundFusion CS4624 support working yet?
I have a Hercules Gamesurround Fortissimo II (replaced my AWE64). It wasn't clear if the OSS modules included with kernel 2.2.19 supported it, so I decided to give ALSA a try. I downloaded and installed ALSA 0.5 some time ago. While the modules detected my card and configured themselves just fine, I got no sound out of the speakers. (Yes, I used alsamixer to turn up the volume on the appropriate channels.)
Someone on the alsa-user mailing list suggested it might have something to do with the "power management" on the newer chip, and to try ALSA 0.9.something (alpha-ware), which has code to handle it. So I did. It compiled, installed, detected my card, and configured itself just fine. alsamixer opens and lets me fool with sliders without trouble. Even the OSS compatibility modules come up fine. But I still can't hear anything.
I haven't touched it since then, as I've been consumed by other distractions. Clearly I'm doing something wrong. But I'm at a complete loss as to what it might be.
Schwab
Editor, A1-AAA AmeriCaptions
All i want is audigy support. p-p-p-phullleeze
i just put in
Yes, Linus has held back the state of Linux and
also the state of computing by more than 10 years.
Sadly, in their attempt to identify with and
deify Linux, people just don't realize this.