Hi Dmitry,
I've added the parisc-kernel-devel mailing list too, since I expect
that *if* somebody is able to answer your question, it will probably
be on the parisc-kernel-devel list...
On 31.03.2015 00:11, Dmitry the Zuryanovich wrote:
As I understand, E class (in my case - E25) has LASI based 53c710
which is handled by 53c700.c? (and in case of workstations wrapped by
lasi700 - what's for? Just for detecting it?)
If I know that that's
5. Sahp Baat Kiuh SCSI at 0xfff74000 [56/52] {4, 0x0, 0x044, 0x00039}
, is there a reason to try to
#modprobe 53c700 clock=25 base=0xfff74000
Looking at drivers/scsi/lasi700.c, it seems the lasi700 driver sets
additional flags like force_le_on_be, chip710, burst_length and so on.
In addition, the IRQs gets connected via drivers/parisc/lasi.c (see lasi_choose_irq()).
I assume you would need at least a "case 0x39" in there.
But James is the expert on the 53c700 driver, so he might know more... ?
[correct my syntax] and may I expect this to work somehow?
What's the problem with SCSI on E class? Is that a need of some
driver which calls 53c700.c with correct parameters taken from
hardware? Can it be just passed to module via parameter or the
problem is deeper?
It might be deeper.
In arch/parisc/kernel/hardware.c I see:
{HPHW_A_DMA, 0x044, 0x00039, 0x80, "Sahp Baat Kiuh SCSI"},
while other SCSI drivers on LASI have HPHW_FIO, e.g.:
{HPHW_FIO, 0x016, 0x00082, 0x0, "Gecko Core SCSI"},
For reference, here is the full dmesg from Dmitry when he tried to boot his E25
machine with a recent Linux kernel:
ftp://parisc.parisc-linux.org/dmesg/E25.dmesg (http://pastebin.com/sXqUjVub)
Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
