Very Computer

    I have a Mitsumi CD (the original one) and am using a Sound Blaster
    MultiCD. The I/O address is set to 0x320 and not 0x300. I rebuilt
    the kernel and now its looking at 0x300. How can I change this?

    There is a line in the mcd.c that sets BASE_ADDR but I don't know
    where it gets the value from.

    I am using the Yggdrasil Plug & Play Summ '94.

   Thanks

   -Nick

--
Nicholas Brenckle                    |  Its all part of my master plan to
Armstrong State College              |             Rule the World.
Computer Information Services        |

Shawn

--

find /usr/src/linux -name mcd.h -print

If you didn't know the file to look for was mcd.h you might have tried

find /usr/src/linux -exec grep BASE_ADDR {} \; -print|less, but that might
find a number of files, of course grep would report the file names and you'd
notice mcd.h, adding a -name \*.h in front of the -exec would make the search
quicker, and you'd be assuming (likely) that the assignment would be found
in a header file.

/usr/src/linux/include/linux/mcd.h by the way...
--
<a href=:"http://www.veryComputer.com/.*ia.EDU/~jeg7e/">Jon Gefaell's Home Page</a>
_____________________________________________________________________________
\ \  /  Jon Gefaell, Computer Systems Engineer       | Amateur Radio, KD4CQY
 \/\/  Community Internetwork Research & Development | -Will chmod for Food-

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 DoD #1439 '82 CB900F "The Turing Machine" | B4 t+ w++ dc g++ k+ s+ m r p++

 I found it. Thanks. I changed the BASE_ADDR from what it was (I don't
 know where the number was comming from) to 0x320 and recompiled. Its
 fine now. No problems.

 -Nick

--
Nicholas Brenckle                    |  Its all part of my master plan to
Armstrong State College              |             Rule the World.
Computer Information Services        |

        [ ...snip happens... ]

Quote:>If you didn't know the file to look for was mcd.h you might have tried

>find /usr/src/linux -exec grep BASE_ADDR {} \; -print|less

    find /usr/src/linux -name '*.h' -print | xargs egrep BASE_ADDR | less

think about process creation/termination... then you'll realize why the
above is *far* more efficient.

btw, many moons ago i ran some tests on fgrep vs egrep vs grep; egrep won
every contest, even for fixed strings.  in fact it was, on average, about
*3* times faster than fgrep.  go figure.

i'm beginning to believe the other grep's are kept around merely for
nostalgia.  :->

gears,
ye wilde ryder
--

"E Pluribus Unix" | 79 it250 "mr. reliable"
"Criminals (especially tyrants) prefer unarmed victims."
"Ignorance can be cured; stupidity, on the other hand, is hereditary."

However. fgrep has no excuse for being slower. It ought to be bashed,
only bash is really slow.
--

 Tel: +49-241-72419 Fax: +49-241-79502
 Goethestr. 20, D-52064 Aachen

GNU fgrep is (should be) just a link to GNU grep, and so is GNU egrep.
In the past GNU fgrep was a separate package, and it sounds like you
have that old (slow!) version.

+--- David Kastrup:
| Well, I don't know about fgrep, but grep can do things egrep can't.
| In short, egrep can be implemented by a finite automaton, grep
| can't. This is due to the \1-\9 things.

Egrep has OR (|), so egrep can do things grep can't do, too.

Kjetil T.