[ECOS] Re: CF disk/FAT16 problem

[ECOS] Re: CF disk/FAT16 problem

[Stéphane Royo]

Hi Savin,

Now, I call the mount function with the appropriate device name
(/dev/disk0/1) but that does not solve my problem, the read boot record
function fails because it reads the sector 0 on my CF instead of 33.

Stephane


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CF disk/FAT16 problem

[Savin Zlobec]

Stéphane Royo wrote:

>Hi Savin,
>
>Now, I call the mount function with the appropriate device name
>(/dev/disk0/1) but that does not solve my problem, the read boot record
>function fails because it reads the sector 0 on my CF instead of 33.
>  
>
Try enabling DEBUG define in disk.c, this will produce several printouts
about the MBR partitions geometry. If you can't figure it out then send the
data to me and I will take a look.

savin

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CF disk/FAT16 problem

[Savin Zlobec]

Stéphane Royo wrote:

>Thank you Savin, but I think that I used the appropriate device name
>/dev/disk0/0 (0 because I have only one partition), have you got an another
>idea ?
>  
>
/dev/disk0/0 is the device handle for the whole disk, to access the 
first partition
use /dev/disk0/1.

>For the fsync function I find it into io.cxx file, could you confirm me that
>I call it directly without  use any upper layer ?
>  
>
upper layer?  ... fsync as in 'int fsync(int fd)' as defined by POSIX 
(prototype in unistd.h)

savin

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re:CF disk/FAT16 problem

[Stéphane Royo]

Thank you Savin, but I think that I used the appropriate device name
/dev/disk0/0 (0 because I have only one partition), have you got an another
idea ?

For the fsync function I find it into io.cxx file, could you confirm me that
I call it directly without  use any upper layer ?

Stephane


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: CF disk/FAT16 problem

[Savin Zlobec]

Stéphane Royo wrote:

>Hello,
>
>I ported V85X CF disk package to another platform and I use eCos FAT16 file
>system package.
>But I have a small problem. For example when I call the mount function the
>read boot record
>fail because the starting block number where begins the reading is 0 but the
>my boot record
>begins at block number 32 for the first partition. To solve temporary this
>problem I set an offset
>according to the partition number when V85X CF disk lookup is called.
>But I don't know if this patch is normal, if is there an another solution.
>  
>
The partition table should be read by the upper layer and all you need 
to do is
to use the appropriate device name - like /dev/disk0/[1-4],   [1-4] is 
the number
of primary partition.

>I would like to know if there is an another solution to flush the file
>system cache to use the unmont ?
>  
>
fsync


savin

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss