On 05.03.2018 03:11, Michael Schmitz wrote:
Hi Finn,
On Mon, Mar 5, 2018 at 2:01 PM, Finn Thain wrote:
On Mon, 5 Mar 2018, Michael Schmitz wrote:
+fail_unmap_dma_regs:
+ if (ioaddr > 0xff)
+ iounmap(esp->dma_regs);
I think you need to test
On 09.08.2014 01:25, Michael Schmitz wrote:
Hi Tuomas,
There's still the Amiga Zorro ESP patch out in limbo - DaveM
suggested a change to enable SCSI-2 features to help with extended
message bytes but that did not work as intended. Haven't had time to
follow that one up. Tuomas' fix to the
On 08.08.2014 11:58, Michael Schmitz wrote:
Hi Ingo,
Am 05.08.2014 um 21:40 schrieb Geert Uytterhoeven
ge...@linux-m68k.org:
m68k v3.16 is out!
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
m68k-queue is getting smaller, but there are still a few commits left:
Hmm,
On 08.08.2014 11:38, Michael Schmitz wrote:
There's still the Amiga Zorro ESP patch out in limbo - DaveM suggested
a change to enable SCSI-2 features to help with extended message bytes
but that did not work as intended. Haven't had time to follow that one
up. Tuomas' fix to the driver to
On 14.04.2014 12:01, Michael Schmitz wrote:
Hi Dave,
When this bit is set, the 53CF94/96 can receive 3-byte messages during
bus-initiated Select With ATN. This feature is also enabled by setting
bit 3 in the Configuration 2 register.
My preference would be to set this one (named
On 14.04.2014 05:14, David Miller wrote:
From: Michael Schmitz schmitz...@gmail.com
Date: Mon, 14 Apr 2014 10:38:09 +1200
That appears to be our problem if I recall correctly Tuomas' debugging
report. (reselection, not selection as initiator). As
esp_slave_configure() enables queue tags
On 09/26/2013 04:44 PM, Michael Schmitz wrote:
Hello Tuomas,
apologies for dropping off the conversation for so long - I only
returned from an overseas trip with only sporadic net access three
days ago.
What exactly does your device support - SCSI-1, SCSI-2 CCS, SCSI-2 or
higher?
On 09/11/2013 05:48 PM, Geert Uytterhoeven wrote:
On Wed, Sep 11, 2013 at 12:12 PM, Michael Schmitz schmitz...@gmail.com wrote:
problem. Using PIO, only the first byte of the tag message comes through. It
might not be esp_scsi's fault, but there seems to be an assumption that all
devices
On 09/11/2013 04:08 PM, Tuomas Vainikka wrote:
On 09/11/2013 01:12 PM, Michael Schmitz wrote:
Hello Tuomas,
That's the attitude - my suggestion was purely pragmatic, in order to
overcome that particular roadblock and see whether there's further
issues. But fixing this properly would be much
On 08/22/2013 11:34 PM, Michael Schmitz wrote:
Hello Tuomas,
No idea which functions you refer to regarding PIO (reading from FIFO).
Anyway, the DMA will read from the same FIFO that the CPU would, if I
understand DMA correctly. There really should be no difference-
esp.scsi.c:1058 versus
On 08/20/2013 12:36 PM, Michael Schmitz wrote:
Tuomas,
I guess those two bytes have something to do with target
(re)selection... There are two different ways of attempting to read
these bytes in the code, one is reading them from the FIFO byte by
byte, and the other way is to setup a DMA
On 08/19/2013 11:48 AM, Michael Schmitz wrote:
Geert,
On Sun, Aug 18, 2013 at 10:58 AM, Michael Schmitz
schmitz...@gmail.com wrote:
I'll also need to check the command_block and command_block_dma
addresses -
does the DMA require virtual or physical addresses?
Physical, of course.
:-) VDMA
On 08/19/2013 11:48 AM, Michael Schmitz wrote:
Geert,
On Sun, Aug 18, 2013 at 10:58 AM, Michael Schmitz
schmitz...@gmail.com wrote:
I'll also need to check the command_block and command_block_dma
addresses -
does the DMA require virtual or physical addresses?
Physical, of course.
:-) VDMA
On 08/17/2013 04:49 AM, Michael Schmitz wrote:
[ 301.88] esp: esp0: Reconnect IRQ2 timeout
Are there interrupts logged for IRQ2 at all (cat /proc/interrupts)? It
looks to me as though all DMA transfers fail (the first command to
fail is READ_CAPACITY which would usually be issued
On 08/16/2013 12:40 AM, Tuomas Vainikka wrote:
On 06/06/2013 11:56 PM, Michael Schmitz wrote:
Geert,
other than 'it compiles', I can't really say much about this one.
I've done what seemed necessary to do the ESP probe setup in the
zorro driver framework (using the NCR7xx driver as a guideline
On 06/06/2013 11:56 PM, Michael Schmitz wrote:
Geert,
other than 'it compiles', I can't really say much about this one.
I've done what seemed necessary to do the ESP probe setup in the
zorro driver framework (using the NCR7xx driver as a guideline),
and used the old Blizzard 2060 driver as a
On 01/09/2012 02:14 PM, Geert Uytterhoeven wrote:
On Mon, Jan 9, 2012 at 11:40, Andreas Schwabsch...@linux-m68k.org wrote:
Alan Hourihaneal...@fairlite.co.uk writes:
*** FORMAT ERROR *** FORMAT=0
Current process id is 768
BAD KERNEL TRAP:
Modules linked in:
PC: [29de]
On 08/08/2011 03:23 AM, Michael Schmitz wrote:
Hi Christian,
Christian - can you remember which 2.6 kernel that last had ethernet
working for you?
I haven't been testing kernels a lot recently... from the logfiles it would
seem the last kernel that was running on kullervo was this one:
Linux
On 08/04/2011 11:45 PM, Michael Schmitz wrote:
On Fri, Aug 5, 2011 at 4:59 AM, Tuomas Vainikka
tuomas.vaini...@aalto.fi wrote:
Hello,
The other network drivers were previously compiled as modules, and I only
had apne built-in.
Now I removed the other drivers being built in any way, but I
On 08/02/2011 08:33 AM, Finn Thain wrote:
On Mon, 1 Aug 2011, Tuomas Vainikka wrote:
NETDEV WATCHDOG: eth0 (): transmit queue 0 timed out
...
eth0: Tx timed out, lost interrupt? TSR=0x4, ISR=0x15, t=52.
eth0: Tx timed out, lost interrupt? TSR=0x5, ISR=0x3, t=33.
eth0: Tx timed out, lost
Hello,
This happens with both stable 3.0.0 and 2.6.39.3 kernels:
[ cut here ]
WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x1a4/0x1c4()
NETDEV WATCHDOG: eth0 (): transmit queue 0 timed out
Modules linked in: nfsd exportfs ipv6 gayle parport_amiga amiflop
21 matches
Mail list logo