Moin,
> -Original Message-
> From: mirabilos [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 29, 2001 1:07 AM
> To: [EMAIL PROTECTED]; Rogier Wolff
> Subject: Re: Sony Memory stick format funnies...
>
>
> Yn).
> > 04e30 00 00 00 00 00 00 4
Moin,
-Original Message-
From: mirabilos [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 1:07 AM
To: [EMAIL PROTECTED]; Rogier Wolff
Subject: Re: Sony Memory stick format funnies...
Yn).
04e30 00 00 00 00 00 00 46 41 54 31 32 20 20 20 00 00 ..FAT12
I've seen something similar with USB memory stick devices... they don't
seem to report a media change in a way that the VFS layer will understand.
I think this deserves some _serious_ debugging, personally, as this is
going to come back to haunt us over and over again with some types of
memory
H. Peter Anvin wrote:
> Rogier Wolff wrote:
> > The image of the disk (including partition table) is at:
> >
> > ftp://ftp.bitwizard.nl/misc_junk/formatted.img.gz
> >
> > It's 63kb and uncompresses to the 64Mb (almost) that it's sold as.
> >
>
> And on at least this kernel (2.4.0)
Btw, the root dir contains 512 entries.
Just from the dump.
(I would let the partition start at sector ptabl+1, not wasting
so much space... but M$ fdisk.exe neither does.)
-mirabilos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
mirabilos wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Btw, the root dir contains 512 entries.
> Just from the dump.
Jep.
> (I would let the partition start at sector ptabl+1, not wasting
> so much space... but M$ fdisk.exe neither does.)
This was formatted by my Sony
Rogier Wolff wrote:
>
> H. Peter Anvin wrote:
> > Gregory Maxwell wrote:
> > > >
> > > > I doubt the kernel is seeing it without it being there (it doesn't have
> > > > much imagination.) However, it may very well be there in a funny
> > > > manner. You do realize, of course, that it's pretty
H. Peter Anvin wrote:
> Gregory Maxwell wrote:
> > >
> > > I doubt the kernel is seeing it without it being there (it doesn't have
> > > much imagination.) However, it may very well be there in a funny
> > > manner. You do realize, of course, that it's pretty much impossible for
> > > us to
Rogier Wolff wrote:
> >
> > I doubt the kernel is seeing it without it being there (it doesn't have
> > much imagination.) However, it may very well be there in a funny
> > manner. You do realize, of course, that it's pretty much impossible for
> > us to help you answer that question without a
Gregory Maxwell wrote:
> On Sun, Apr 29, 2001 at 01:09:22PM -0700, H. Peter Anvin wrote:
> > Rogier Wolff wrote:
> > >
> > > H. Peter Anvin wrote:
> > > > Followup to: <[EMAIL PROTECTED]>
> > > > By author:[EMAIL PROTECTED] (Rogier Wolff)
> > > > In newsgroup: linux.dev.kernel
> > > > >
> >
H. Peter Anvin wrote:
> Rogier Wolff wrote:
> >
> > H. Peter Anvin wrote:
> > > Followup to: <[EMAIL PROTECTED]>
> > > By author:[EMAIL PROTECTED] (Rogier Wolff)
> > > In newsgroup: linux.dev.kernel
> > > >
> > > > # l /mnt/d1
> > > > total 16
> > > > drwxr-xr-x 512 root root
Gregory Maxwell wrote:
> >
> > I doubt the kernel is seeing it without it being there (it doesn't have
> > much imagination.) However, it may very well be there in a funny
> > manner. You do realize, of course, that it's pretty much impossible for
> > us to help you answer that question without
On Sun, Apr 29, 2001 at 01:09:22PM -0700, H. Peter Anvin wrote:
> Rogier Wolff wrote:
> >
> > H. Peter Anvin wrote:
> > > Followup to: <[EMAIL PROTECTED]>
> > > By author:[EMAIL PROTECTED] (Rogier Wolff)
> > > In newsgroup: linux.dev.kernel
> > > >
> > > > # l /mnt/d1
> > > > total 16
> > >
Rogier Wolff wrote:
>
> H. Peter Anvin wrote:
> > Followup to: <[EMAIL PROTECTED]>
> > By author:[EMAIL PROTECTED] (Rogier Wolff)
> > In newsgroup: linux.dev.kernel
> > >
> > > # l /mnt/d1
> > > total 16
> > > drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
> > > -r-xr-xr-x 1
H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:[EMAIL PROTECTED] (Rogier Wolff)
> In newsgroup: linux.dev.kernel
> >
> > # l /mnt/d1
> > total 16
> > drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
> > -r-xr-xr-x 1 root root0 May 23 2000
H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
# l /mnt/d1
total 16
drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
-r-xr-xr-x 1 root root0 May 23 2000 memstick.ind*
Rogier Wolff wrote:
H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
# l /mnt/d1
total 16
drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
-r-xr-xr-x 1 root root
On Sun, Apr 29, 2001 at 01:09:22PM -0700, H. Peter Anvin wrote:
Rogier Wolff wrote:
H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
# l /mnt/d1
total 16
drwxr-xr-x 512 root root
Gregory Maxwell wrote:
I doubt the kernel is seeing it without it being there (it doesn't have
much imagination.) However, it may very well be there in a funny
manner. You do realize, of course, that it's pretty much impossible for
us to help you answer that question without a
H. Peter Anvin wrote:
Rogier Wolff wrote:
H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
# l /mnt/d1
total 16
drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
Rogier Wolff wrote:
I doubt the kernel is seeing it without it being there (it doesn't have
much imagination.) However, it may very well be there in a funny
manner. You do realize, of course, that it's pretty much impossible for
us to help you answer that question without a complete
Gregory Maxwell wrote:
On Sun, Apr 29, 2001 at 01:09:22PM -0700, H. Peter Anvin wrote:
Rogier Wolff wrote:
H. Peter Anvin wrote:
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
# l /mnt/d1
total 16
H. Peter Anvin wrote:
Gregory Maxwell wrote:
I doubt the kernel is seeing it without it being there (it doesn't have
much imagination.) However, it may very well be there in a funny
manner. You do realize, of course, that it's pretty much impossible for
us to help you answer
Rogier Wolff wrote:
H. Peter Anvin wrote:
Gregory Maxwell wrote:
I doubt the kernel is seeing it without it being there (it doesn't have
much imagination.) However, it may very well be there in a funny
manner. You do realize, of course, that it's pretty much impossible for
mirabilos wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
Btw, the root dir contains 512 entries.
Just from the dump.
Jep.
(I would let the partition start at sector ptabl+1, not wasting
so much space... but M$ fdisk.exe neither does.)
This was formatted by my Sony DSC505V.
Btw, the root dir contains 512 entries.
Just from the dump.
(I would let the partition start at sector ptabl+1, not wasting
so much space... but M$ fdisk.exe neither does.)
-mirabilos
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
H. Peter Anvin wrote:
Rogier Wolff wrote:
The image of the disk (including partition table) is at:
ftp://ftp.bitwizard.nl/misc_junk/formatted.img.gz
It's 63kb and uncompresses to the 64Mb (almost) that it's sold as.
And on at least this kernel (2.4.0) there is nothing
I've seen something similar with USB memory stick devices... they don't
seem to report a media change in a way that the VFS layer will understand.
I think this deserves some _serious_ debugging, personally, as this is
going to come back to haunt us over and over again with some types of
memory
Michael Rothwell wrote:
>
> From: "H. Peter Anvin" <[EMAIL PROTECTED]>
> > "dcim" probably stands for "digital camera images". At least Canon
> > digital cameras always put their data in a directory named dcim.
>
> Makes sense. FAT's root directory is limited in the number of entries it can
>
From: "H. Peter Anvin" <[EMAIL PROTECTED]>
> "dcim" probably stands for "digital camera images". At least Canon
> digital cameras always put their data in a directory named dcim.
Makes sense. FAT's root directory is limited in the number of entries it can
contain, to something like 32. Cameras
Followup to: <[EMAIL PROTECTED]>
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
>
> # l /mnt/d1
> total 16
> drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
> -r-xr-xr-x 1 root root0 May 23 2000 memstick.ind*
> #
>
> Where the
> 001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 02
> 001c0 08 00 01 07 d0 dd 27 00 00 00 d9 ee 01 00 00 00
P]'...Yn
> 001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
..U*
> 04e00 e9 00 00 20 20 20 20 20 20 20 20 00 02 20 01 00 i..
Hi,
I have a Sony memory stick in my system. When I display all the
interesting (i.e. not all 0xff and not all 0x00 data), I see (on a
recently formatted stick):
% hd /dev/hde | grep -v "ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff" | grep -v
"00 00 00 00 00 00 00 00 00 00 00 00 00 00
Hi,
I have a Sony memory stick in my system. When I display all the
interesting (i.e. not all 0xff and not all 0x00 data), I see (on a
recently formatted stick):
% hd /dev/hde | grep -v ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff | grep -v
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 02
001c0 08 00 01 07 d0 dd 27 00 00 00 d9 ee 01 00 00 00
P]'...Yn
001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
..U*
04e00 e9 00 00 20 20 20 20 20 20 20 20 00 02 20 01 00 i....
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Rogier Wolff)
In newsgroup: linux.dev.kernel
# l /mnt/d1
total 16
drwxr-xr-x 512 root root16384 Mar 24 17:26 dcim/
-r-xr-xr-x 1 root root0 May 23 2000 memstick.ind*
#
Where the *(#$% does
From: H. Peter Anvin [EMAIL PROTECTED]
dcim probably stands for digital camera images. At least Canon
digital cameras always put their data in a directory named dcim.
Makes sense. FAT's root directory is limited in the number of entries it can
contain, to something like 32. Cameras can easily
Michael Rothwell wrote:
From: H. Peter Anvin [EMAIL PROTECTED]
dcim probably stands for digital camera images. At least Canon
digital cameras always put their data in a directory named dcim.
Makes sense. FAT's root directory is limited in the number of entries it can
contain, to
38 matches
Mail list logo
