Re: [H2200-port] HAMCOP NAND driver

[Joshua Wise <joshua@joshuawise.com>]

> I can't recall exactly, but I probably put it there because it seemed 
> like it ought to live with the rest of its SoC brethren, or it was 
> easier. I think my first version did live in with mtd. It doesn't matter 
> to me where it lives.
Okay. Later today, I will throw it into the MTD tree (probably flip it 
over to the MTD list first to make sure that there's nothing too too 
wrong with it). I'll probably also change it to use a variable SHAMCOP 
base, as I'm going to be using that with a JTAG MTD mapping driver too.

> Write support is there, but I haven't had the courage to try it out. :-) 
> There is a write_enable module_param for shamcop_nand, which if set to 1 
> would theoretically allow writes (which amounts to just setting the 
> write enable bit).
Awesome! I will see what I can do later.

> Now that you're all set up with JTAG, you seem like the best person to 
> try it out. :-)
Ah, I'm almost set up with JTAG here. It seems that indeed when we 
doodle with CPU jtag, it leaves SHAMCOP JTAG in a funny state, which 
essentially amounts to making the SHAMCOP useless. Tomorrow I'll ask 
Jamey if there's a trace that I should be cutting to disable TDI on 
SHAMCOP. (Alternatively, we also have JTAG direct on SHAMCOP, although 
as noted previously, I don't know the boundary scan order for that.)

joshua