From: Toshiharu N. <no...@hi...> - 2000-06-07 10:17:43
|
Thank you for an opinion. I confirmed whether other Solution Engine worked. Solution Engine of SH3(09A) worked. but, it will work only with my boot environment. there was still a lot of problems. kaz Kojima wrote: > causes problem by the magic number 0x3000. It's not bad to initialize > sh_pcic_io_start and sh_pcic_io_stop but they will cheaged by PCMCIA > driver like pcmcia-cs. Nozawa-san, you can't handle these variable > as constants. OK. I understand. Probably, I thought so. I will revise this. > > It seems that your comments above means we need this "0x400000" for > > byte access of "read" (in). Is there any reason why we don't need > > this "0x40000" for "write" (out)? > > This chip is odd enough. These four 256KB spaces are exactly same in > write access. According to the manual of MRSHPC, there was resize to PCMCIA bus. On this account byte/word space every 256KByte thinks that there is not semantics. Then, I have decided to do every access to real-word space. Is this wrong? (However, this is the cause of confusion.) -- |