Re: ddb write and io memory

[Frank Wille <frank%phoenix.owl.de@localhost>]

matthew green wrote:

>    On Sat, Jan 30, 2010 at 08:45:48PM +0100, Frank Wille wrote:
>> Therefore I would like to change ddb/db_write_cmd.c as in the
>>    following ch:
>> [...]
>> 
>> Any objections? Do we absolutely need to print the old value here?
>    
>    I think it's somewhat desirable to. Wouldn't it be better anyway to
>    create a second command ("iowrite" or "regwrite" or something) that
>    both does this and also does anything else that might be necessary
>    to write to I/O registers safely, like flushing caches?
>
> yeah - please invent a new commamd

Ok. I make a new command. iowrite sounds nice.


> (maybe even "mach" command) to
> do this, instead of changing how write works.

I doubt that a machine command makes much sense, because I see no machine
dependency in not reading memory before writing it.

Flushing caches should be done anyway in the MD backend of db_memwr.c.

-- 
Frank Wille