Subject: Re: mmem woes
To: None <port-dreamcast@netbsd.org>
From: Harold Gutch <logix@foobar.franken.de>
List: port-dreamcast
Date: 02/08/2003 10:54:38
On Sat, Feb 08, 2003 at 09:45:55AM +0900, ITOH Yasufumi wrote:
> logix@foobar.franken.de writes:
>
> > These messages repeat all the time. Also, I am unable to do
> > anything with it, like dd away from it, since it gets detached
> > too quickly again.
>
> Hmm, the driver fails to detect unit presense....
> What is printed around detach if you add
>
> options MAPLE_DEBUG=2
>
> to the kernel config file?
mmem0 detached
maple0: no request 1
maple0: no request 2
mapleA: unit_map 0x20 -> 0x21 (units 0x3)
maple0: no request 1
maple0: no request 2
maple0: no request 3
maple0: no request 4
maple0: no request 5
maple0: no request 6
mapleA1 at maple0 port 0 subunit 1: a 0x2 c 0 fn 0xe d 0x7e7e3f40,0x51000,0xf410
0: Visual Memory
mmem0 at mapleA1 function 1: Memory card
mmem0: 1 part, 512 bytes/block, 4 acc/write, 1 acc/read
mapleA1 function 2 not configured
mapleA1 function 3 not configured
mmem0.0: 128 KB, blk 255 0, inf 255, fat 254 1, dir 253 13, icon 8, data 241
maple0: no request 1
maple0: no request 2
maple0: no request 3
maple0: no request 4
maple0: no request 1
maple0: no request 2
maple0: no request 3
maple0: no request 4
maple0: no request 5
maple0: no request 6
mapleA1: ping response -1
mapleA1: remove
mapleA1: detaching func 1
mmem0 detached
Again, all of this is repeated all the time. Would increasing
MAPLE_DEBUG to 3 help?
bye,
Harold