[lkml]   [2001]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Qlogic/FC firmware
>>>>> "David" == David S Miller <> writes:

David> From: Jes Sorensen <> Date: 21 Aug 2001
David> 15:51:55 +0200

> The much cleaner way to solve this problem is to write a
> user space tool to upgrade the image in the flash ram on the QL
> with your latest favorite image found at It's a
> 128KB image, you can write directly to the flash in two banks
> by setting the read/write bit and setting the 2nd bank bit for
> the last 64KB.

David> When the Qlogic,FC sees a master abort, the firmware is
David> essentially cleared to zero.

David> This is what was happening to me.

Ehm, isn't the firmware only cleared to zero in the runtime memory or
are you saying that they nuke their flash ram as well? If the flash
ram is safe, you should still be able to boot any kernel and go from
there after you reset the adapter.

Clearing the firmware is still utterly stupid, but thats a firmware
stupidity. It is actually possibly to find the binary firmware image
out in the flash, but it's located at a weird location that makes me
suspect that they have some directory structure which I do not know

David> If you're going to say "put the user thing in initrd", I'm
David> going to say "bite me". I build a static kernel with no initrd
David> and that is how I'd like it to stay. It is one thing to do
David> initrd firmware loading for devices not necessary for booting
David> and mounting root, that is acceptable, this isn't.

Well I thought Linus said we were going to have a required init
ramdisk for 2.5 anyway. But thats of course an unknown amount of time

David> Jes, I think your arguments are wrong. I think the driver
David> should have been removed in whole and replaced with something
David> like this in qlogicfc.c so everyone would know what the problem
David> is:

I disagree, the driver will still work just fine for people who have
the cards in machines such as PCs. I do agree however that it would
probably have been a good idea to leave a note in there stating why it
was removed.

However the reason I barked was because of you suggesting we remove
all firmware or should just have left it in there. If we have a GPL
violation then IMHO it has to be dealt with immediately, then we can
look at the damages afterwards.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:57    [W:0.047 / U:1.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site