[PlanetCCRMA] HDSP 9652 patch

[Mark Knecht]

Janina,
   Hi. Well, as for the dependencies, if I was to uninstall Alsa I'd get
forced to uninstall all sorts of other things, so I'm just being careful
since I don't really know too much about this stuff. Also, when I
started with these groups about 3 months ago, I was trying to be
partially RPM based and partially code based. While that's still true,
I'd prefer to be mostly RPM based if possible.

   As for the driver, the 'offending' file, if that's the right name for
it, is hdsp.o. All I was thinking was that I now know the patch, which I
could do by hand to hdsp.c, then compile it to hdsp.o, and then place it
where the current hdsp.o file is.

   Assuming that this doesn't break linkages, I'd reboot and be running
the new one. To me that seems like the simplest solution right now.

   The moment I hear that Fernando has applied this patch and done an
rpm for me, that would be my real solution.

Mark


On Sun, 2002-12-08 at 10:29, Janina Sajka wrote:
> Mark Knecht writes:
> > 
> > Apparently the (rev 64) part I'm seeing
> > in alsaconf is what needs to be patched into the hdsp driver.
> > 
> >    I'm willing to try and do this, but I've never patched driver code,
> > much less much of anything else. (!! time to learn I suppose!!)
> > 
> >    I'm wondering if I could just build the hdsp driver _only_ and then
> > copy it to the right location by hand, until you can get this into an
> > alsa update for testing. I don't want to break my rpm dependencies...
> > 
> But, if you build a driver by hand, you'll break them right there,
> unless you also go through the processing of gening a new srpm and rpm.
> 
> My question for you, though, is "what dependencies?" Typically, the only
> dependencies against an ALSA driver are everything else beyond it--which
> has to get replaced anyway if you change ALSA versions. On the other
> hand, if you patch an existing ALSA version and gen the rpm, you won't
> actually break those dependencies. So, if you're going to try to create
> a patched driver, why not ignore the deps, as you'll be replacing the
> linkage.
> 
> I don't recall whether or not you have other audio devices, or what
> version ALSa you have. Those would certainly be factors for informing a
> best approach. All else being equal, my own predeliction would be for
> the newer ALSA.
> >    Any comments on how to best proceed warmly welcomed. This looks like
> > the answer to me.
> > 
> > Thanks,
> > Mark
> > 
> > 
> > 
> > <SNIP>
> > 
> >  can the person who fixed their hdsp driver to work with the new 9652
> >  please post a patch (c/o diff -u) here? i would like to get the fix
> >  into CVS ...
> >  
> >  --p
> >  
> > 
> > 
> >       From: Justin Cormack <justin@st...>
> >       Re: hdsp/new 9652  
> >       2002-12-03 11:36
> > 
> >  On Tue, 2002-12-03 at 19:00, Paul Davis wrote:
> >  > can the person who fixed their hdsp driver to work with the new 9652
> >  > please post a patch (c/o diff -u) here? i would like to get the fix
> >  > into CVS ...
> >  > 
> >  
> >  there wasnt much, assuming that Takashi's patch is in cvs, which I
> > think
> >  it is.
> >  
> >  Any news on mixer support? There seem to be Windows and Mac drivers
> > with
> >  mixer suuport now.
> >  
> >  It was only:
> >  
> >  --- hdsp.c-orig 2002-12-03 19:28:40.000000000 +0000
> >  +++ hdsp.c      2002-12-03 19:28:06.000000000 +0000
> >  @@ -2966,6 +2966,7 @@
> >  
> >          switch (rev & 0xff) {
> >          case 0xa:
> >  +       case 0x64:
> >                  /* hdsp_initialize_firmware() will reset this */
> >                  hdsp->card_name = "RME Hammerfall DSP";
> >                  break;
> >  
> > 
> > 
> > _______________________________________________
> > PlanetCCRMA mailing list
> > PlanetCCRMA@ccrma.stanford.edu
> > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> 
> -- 
> 	
> 				Janina Sajka, Director
> 				Technology Research and Development
> 				Governmental Relations Group
> 				American Foundation for the Blind (AFB)
> 
> Email: janina@afb.net		Phone: (202) 408-8175
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma