Re: asm_pci.h,v Holy cow!

2000-04-27 Thread Peter Jeremy
On Tue, Apr 25, 2000 at 09:48:18PM +1000, Sheldon Hearn wrote: If that's the _only_ point, then Garrett Wollman's idea should work perfectly. Stick the files under CVS, just agree that they should never be revised, but rather that new versions should be imported in a different directory and the

Re: asm_pci.h,v Holy cow!

2000-04-27 Thread Garrett Wollman
On Fri, 28 Apr 2000 09:37:40 +1000, Peter Jeremy [EMAIL PROTECTED] said: How do you suggest such files get distributed? cvsup and/or rsync. This does leave CTM-users the odd men out As Matt pointed out, CVS provides us with a good mechanism for ensuring that I can identify what version

Re: asm_pci.h,v Holy cow!

2000-04-27 Thread Matthew Jacob
I don't see the purpose of having a firmware image permanently resident (especially given their sizes). Getting the boot loader to directly load the firmware into the device seems a much nicer solution. If this is impractical, treating the firmware as a kld and unloading it after

Re: asm_pci.h,v Holy cow!

2000-04-25 Thread Sheldon Hearn
On Mon, 24 Apr 2000 13:52:20 MST, Matthew Jacob wrote: But this isn't the point. The point is to cause less cvsup turbulence for all and sundry. I think I can do enough of this by just splitting the file apart to keep everyone happy. Or happy enough. If that's the _only_ point, then

Re: asm_pci.h,v Holy cow!

2000-04-25 Thread Garrett Wollman
On Tue, 25 Apr 2000 13:47:03 +0200, Sheldon Hearn [EMAIL PROTECTED] said: If that's the _only_ point, then Garrett Wollman's idea should work perfectly. Stick the files under CVS No, that was not my proposal. I want to keep them out of CVS entirely. CVS is Not Good at handling binary files

Re: asm_pci.h,v Holy cow!

2000-04-25 Thread Nate Williams
If that's the _only_ point, then Garrett Wollman's idea should work perfectly. Stick the files under CVS No, that was not my proposal. I want to keep them out of CVS entirely. CVS is Not Good at handling binary files (even if you never change them). That's why I'd like them in a

asm_pci.h,v Holy cow!

2000-04-24 Thread Julian Elischer
My cvsup appeared to be frozen, so I stopped it and looked.. src/sys/dev/isp/asm_pci.c,v is 13MB long! it was just taking a long time.. this seems a little excessive. anyone got any ideas. (13MB on a 40Kbit link is a long time) to make matters worse cvsup appears to be redownloading some

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Bruce Evans
On Mon, 24 Apr 2000, Julian Elischer wrote: My cvsup appeared to be frozen, so I stopped it and looked.. src/sys/dev/isp/asm_pci.c,v is 13MB long! it was just taking a long time.. this seems a little excessive. I was annoyed by this a few months ago when the file was only 10MB.

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Matthew Jacob
Yes, this needs to be fixed. I have an open bug about this with respect to making the f/w a loadable module as well. I'll probably split it into several pieces so that each f/w update is smaller. I could probably make it binary and compress is (each f/w module is an array of 16 bit shorts), but

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Julian Elischer
Garrett Wollman wrote: On Mon, 24 Apr 2000 21:30:01 +1000 (EST), Bruce Evans [EMAIL PROTECTED] said: This seems to be inherent in the file format. Binary data is expanded by a factor of 4 due to encoding it as a C array. Even tiny changes in the data ripple through the array and give

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Richard Wackerbarth
On Mon, 24 Apr 2000, Julian Elischer wrote: This seems well thought out and I certainly agree that we don't need DIFFs of firmware. I wonder if we can somehow "cheat time" and get that 13MB file out of the source tree and retro-actively tag the new scheme so that we don't have to carry it

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Wilko Bulte
On Mon, Apr 24, 2000 at 01:43:44PM -0500, Richard Wackerbarth wrote: On Mon, 24 Apr 2000, Julian Elischer wrote: This seems well thought out and I certainly agree that we don't need DIFFs of firmware. I wonder if we can somehow "cheat time" and get that 13MB file out of the source tree

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Richard Wackerbarth
On Mon, 24 Apr 2000, you wrote: Seriously, perhaps we should consider putting optional pieces of the kernel Firmware for a SCSI adapter is not optional. At least not on some of the Alpha machines that download out-of-date firmware from their SRMs so depend on the driver to load them with

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Wilko Bulte
On Mon, Apr 24, 2000 at 02:07:22PM -0500, Richard Wackerbarth wrote: On Mon, 24 Apr 2000, you wrote: Seriously, perhaps we should consider putting optional pieces of the kernel Firmware for a SCSI adapter is not optional. At least not on some of the Alpha machines that download

Re: asm_pci.h,v Holy cow!

2000-04-24 Thread Matthew Jacob
Matt can tell you more ;-) People don't really want to know more. They just don't want what I provide support for to impact them. I'll bet if I sum up all the other kernel mathoms like netgraph, and so on, that *I* never use, it'd be less than this f/w...:-) But this isn't the point. The