Christian Jullien writes: > > I think he is right (or the problem is related to something like that, since > IRQ is never raised), but how can I force this stupid board (remember, a > port replicator!!) to change its behavior? I've not smart BIOS access for > that board except enabled/disabled !! > > Another related question, how I can I force Linux to receive this #@*!~ > interrupt (NT receives it after all) > Isn't it a 'force IRQ to something' somewhere that can help ? Now, I think > it's more an interrupt probleme thant a driver problem. > > Thanks, christian > > Have you checked meanwhile if NT really sees the irq 5 or has just registered it? Egbert. - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
- RE: Linux SCSI seagate (TMC-950) driver hel... Marc SCHAEFER
- RE: Linux SCSI seagate (TMC-950) driver... Christian Jullien
- RE: Linux SCSI seagate (TMC-950) d... Marc SCHAEFER
- RE: Linux SCSI seagate (TMC-95... Christian Jullien
- RE: Linux SCSI seagate (TMC-95... Egbert Eich
- RE: Linux SCSI seagate (TMC-950) driver hel... Egbert Eich
- Re: Linux SCSI seagate (TMC-950) driver hel... Drew Eckhardt
- RE: Linux SCSI seagate (TMC-950) driver help Christian Jullien
- Re: Linux SCSI seagate (TMC-950) driver help Marc SCHAEFER
- RE: Linux SCSI seagate (TMC-950) driver help Egbert Eich
- RE: Linux SCSI seagate (TMC-950) driver help Christian Jullien
- Re: Linux SCSI seagate (TMC-950) driver hel... Drew Eckhardt
- Re: Linux SCSI seagate (TMC-950) driver... Egbert Eich
- RE: Linux SCSI seagate (TMC-950) d... Christian Jullien
- RE: Linux SCSI seagate (TMC-950) driver... Christian Jullien
