Re: m68k v3.16 status update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Finn,

thanks, doing that now. The log is on IDE so no danger there. My debug
code along with esp_debug = ESP_DEBUG_RECONNECT shows the code path is
exercised by the single disk attached to elgar.

Contrary to the Mac driver, esp->command_block and
esp->command_block_dma are not identical addresses on Amiga. Is there
a generic way to map a DMA address (i.e., physical address AFAIK) to a
kernel virtual one? (I can use esp->command_block in the reconnect
message special case but not otherwise ...)

Cheers,

  Michael


On Fri, Dec 15, 2017 at 12:49 PM, Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> wrote:
On Fri, 15 Dec 2017, Michael Schmitz wrote:

Hi Tuomas,

fair enough - I'll get the PIO code tested by forcing PIO transfers on
elgar, and submit the driver for review once that's done.

You might need to instrument the esp_reconnect_with_tag() code path to
confirm that elgar's scsi disks exercise the new code. I'd probably just
set esp_scsi.esp_debug=0x200 (that is, ESP_DEBUG_RECONNECT). But watch out
for /var/log/kern.log, in case it is on a scsi disk...

--

Maybe someone else has a chance to test the fix in the meantime.

Cheers,

  Michael


--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux