HAMCOP NAND driver

HAMCOP NAND driver

[Joshua Wise]

Hi folks,

Is there any reason why HAMCOP NAND driver is not in the MTD directory 
and MTD CVS as all the other NAND drivers are?

Also, what is the status of that driver? A quick flip through seems to 
show that it's only got support for read-in commands, although I'm not 
too familiar with the HAMCOP's NAND architecture. If it's only got read 
support, is someone already working on write? (If not, I will volunteer 
to do that... don't want to duplicate work, though.)

Thanks,
joshua

Re: [H2200-port] HAMCOP NAND driver

[Matthew Reimer]

Hi Joshua.

Joshua Wise wrote:

> Hi folks,
>
> Is there any reason why HAMCOP NAND driver is not in the MTD directory 
> and MTD CVS as all the other NAND drivers are?

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. Where does its cousin S3C2410 NAND driver live?

> Also, what is the status of that driver? A quick flip through seems to 
> show that it's only got support for read-in commands, although I'm not 
> too familiar with the HAMCOP's NAND architecture. If it's only got 
> read support, is someone already working on write? (If not, I will 
> volunteer to do that... don't want to duplicate work, though.)

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).

Now that you're all set up with JTAG, you seem like the best person to 
try it out. :-)

Matt

Re: [H2200-port] HAMCOP NAND driver

[Ben Dooks]

On Thu, Aug 26, 2004 at 02:57:44PM -0700, Matthew Reimer wrote:
> Hi Joshua.
> 
> Joshua Wise wrote:
> 
> >Hi folks,
> >
> >Is there any reason why HAMCOP NAND driver is not in the MTD directory 
> >and MTD CVS as all the other NAND drivers are?
> 
> 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. Where does its cousin S3C2410 NAND driver live?

nowhere atm, there is an 2.4 version which is in the last EB2410ITX
kernel patch I did, and possibly one for the 2.6 to be done.

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

Re: [H2200-port] HAMCOP NAND driver

[Matthew Reimer]

Also see http://handhelds.org/hypermail/h2200-port/8/0876.html .

Matt

Re: [H2200-port] HAMCOP NAND driver

[Joshua Wise]

> 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