Hi, Scott.
On Apr 16 2015, Scott Wood wrote:
> On Thu, 2015-04-16 at 21:01 -0300, Rogério Brito wrote:
> > On Apr 16 2015, Scott Wood wrote:
> > > On Thu, 2015-04-16 at 19:55 -0300, Rogério Brito wrote:
> > > > Is there any "proper" way for me to discover what device name the kernel
> > > > uses?
On Thu, 2015-04-16 at 21:01 -0300, Rogério Brito wrote:
> Dear Scott.
>
> On Apr 16 2015, Scott Wood wrote:
> > On Thu, 2015-04-16 at 19:55 -0300, Rogério Brito wrote:
> > > Is there any "proper" way for me to discover what device name the kernel
> > > uses? I have tried the following command line
Dear Scott.
On Apr 16 2015, Scott Wood wrote:
> On Thu, 2015-04-16 at 19:55 -0300, Rogério Brito wrote:
> > Is there any "proper" way for me to discover what device name the kernel
> > uses? I have tried the following command lines without success:
> >
> > 1 -
> > mtdparts=myflash:4096k(allflash
On Thu, 2015-04-16 at 19:55 -0300, Rogério Brito wrote:
> Hi, Scott and others.
>
> On Apr 09 2015, Rogério Brito wrote:
> > On Apr 09 2015, Scott Wood wrote:
> > > On Thu, 2015-04-09 at 18:54 -0300, Rogério Brito wrote:
> > > >
> > > > mtdparts=myflash:4096k(allflash),3072k(firmimg),448k@307
Hi, Scott and others.
On Apr 09 2015, Rogério Brito wrote:
> On Apr 09 2015, Scott Wood wrote:
> > On Thu, 2015-04-09 at 18:54 -0300, Rogério Brito wrote:
> > >
> > > mtdparts=myflash:4096k(allflash),3072k(firmimg),448k@3072k(bootcode),64k@3520k(status),512k@3584k(conf)
> >
> > What is "myfl
Hi, Scott.
On Apr 07 2015, Scott Wood wrote:
> On Tue, 2015-04-07 at 21:37 -0300, Rogério Brito wrote:
> > I see. If I do some "archaeology" (read: bisect when it stopped
> > working), would that help to discover how the flash is connected?
>
> It will probably give you the address and size of th
On Tue, 2015-04-07 at 21:37 -0300, Rogério Brito wrote:
> Dear Scott,
>
> Once again, thank you very much for your answer.
>
> On Apr 07 2015, Scott Wood wrote:
> > On Tue, 2015-04-07 at 20:58 -0300, Rogério Brito wrote:
> > > This is good to know. Is there any reasonable dts that I can copy/adap
Dear Scott,
Once again, thank you very much for your answer.
On Apr 07 2015, Scott Wood wrote:
> On Tue, 2015-04-07 at 20:58 -0300, Rogério Brito wrote:
> > This is good to know. Is there any reasonable dts that I can copy/adapt?
>
> I'm not familiar with how flash is connected on this chip, so
On Tue, 2015-04-07 at 20:58 -0300, Rogério Brito wrote:
> Dear Scott.
>
> First of all, thank you so very much for your reply.
>
> On Apr 07 2015, Scott Wood wrote:
> > On Sat, 2015-04-04 at 02:40 -0300, Rogério Brito wrote:
> > > ,
> > > | physmap platform flash device: 0040 at ffc0
Dear Scott.
First of all, thank you so very much for your reply.
On Apr 07 2015, Scott Wood wrote:
> On Sat, 2015-04-04 at 02:40 -0300, Rogério Brito wrote:
> > ,
> > | physmap platform flash device: 0040 at ffc0
> > | physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank. Manufac
On Sat, 2015-04-04 at 02:40 -0300, Rogério Brito wrote:
> Unfortunately, right now, what I see with Linus's tree
> (4.0.0-rc6-9-g6c310bc) is the following:
>
> ,
> | physmap platform flash device: 0040 at ffc0
> | physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank. Manufactu
Hi.
I just revived a Kurobox HG to use as a NAS (I also have a simpler Kurobox
HD here, not being used at this moment) and I am having problems that didn't
happen before. I will describe the first problem here and further problems
in later e-mails.
During the 2.6.27 to 2.6.29 era (I may be mista
12 matches
Mail list logo
