On 08/01/2011, at 23:14, Hans Verkuil wrote: >> Looking at some other consumers of that function it would appear the last argument (NULL in this case) is superfluous, however the file appears to be replaced each time I run build.sh so I can't update it. > > Only run build.sh once. After that you can modify files and just run 'make'. > > build.sh will indeed overwrite the drivers every time you run it so you should > that only if you want to get the latest source code. Ahh, I see. Any chance the README could be modified to say something about that? Currently it doesn't mention build.sh at all - I had to google to find anything of use. Perhaps also rename build.sh to setup.sh. Thanks :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
