Vincenzo GRANATO | 6 Jul 2004 08:17

BSD and NAND

Dear all, I’ve some question about NetBSD, does it support NAND FLASH? Is it possible to replace the BSD FS with YAFFS or JFFS? Where do I can find some information about these? Many thanks,Regards,        Vincenzo  

 

!DSPAM:40ea4bb2212111237517854!
Ian Zagorskih | 7 Jul 2004 05:27

Re: BSD and NAND

On Tuesday 06 July 2004 13:17, Vincenzo GRANATO wrote:

> I've some question about NetBSD, does it support
> NAND FLASH?

Officially AFAIK no

> Is it possible to replace the BSD FS with YAFFS or JFFS?

AFAIK no, there's no port of YAFFS or JFFS/JFFS2 for NetBSD

> Where do I can find some  information about these?

AFAIK Wasabi Systems people (http://www.wasabisystems.com) have some NAND (or 
NOR ? I don't remember..) Flash implementation plus journaled FS for NetBSD 
but it isn't available for public domain. You probably should ask them 
directly :)

Take a look at Linux MTD project at http://www.linux-mtd.infradead.org. They 
have done a lot of work and, theoretically, it can be ported/rewritten for 
NetBSD. Though from my personal exp this 1) needs a lot of work 2) Linux MTD 
is poorly documented.

// wbr

josh | 23 Jul 2004 06:33

Atheros Driver, changing ACK timeout?

Is there a way to change the ACK timeout for the atheros driver? 

I want to do some long distance links ( eg, 30km + ) and the default ACK 
timeout is not long enough for the RF to get there and back. As a result, 
DUP packets occur when pinging, and in general performance is horrid. 

Ive looked thru the ath driver stuff, and I could not see anything relating 
to changing the ACK timeout.. perhaps it is in the HAL? 

Any ideas? I dont want to use staros or such like ( which can alter the ACK 
timeout ) 

Thanks 

P.S Oranges and Apples and Pinapples and such fruit tastes good.

Charles M. Hannum | 23 Jul 2004 07:07

Re: Atheros Driver, changing ACK timeout?

On Friday 23 July 2004 04:33, josh wrote:
> Is there a way to change the ACK timeout for the atheros driver?
>
> I want to do some long distance links ( eg, 30km + ) and the default ACK
> timeout is not long enough for the RF to get there and back. As a result,
> DUP packets occur when pinging, and in general performance is horrid.
>
> Ive looked thru the ath driver stuff, and I could not see anything relating
> to changing the ACK timeout.. perhaps it is in the HAL?

Like many things, this is indeed buried in the HAL, which we don't really have 
access to.

How are you propagating the signal 30km?


Gmane