public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V6] sf: Turn SPI flash chip into 3-Byte address mode
Date: Thu, 13 Aug 2015 13:21:05 +0200	[thread overview]
Message-ID: <55CC7DA1.1030605@denx.de> (raw)
In-Reply-To: <CY1PR0301MB07803B4F5C614D1C776E1FFD8B7D0@CY1PR0301MB0780.namprd03.prod.outlook.com>

On 13.08.2015 12:50, Hou Zhiqiang wrote:
>> -----Original Message-----
>> From: Siva Durga Prasad Paladugu [mailto:siva.durga.paladugu at xilinx.com]
>> Sent: 2015?8?13? 17:18
>> To: Hou Zhiqiang-B48286; u-boot at lists.denx.de; jteki at openedev.com
>> Cc: Sun York-R58495; Hu Mingkai-B21284; nofooter
>> Subject: RE: [PATCH V6] sf: Turn SPI flash chip into 3-Byte address mode
>>
>> Hi Zhejiang/Jagan,
>>
>> I think it would be good to extend this further to support 4-byte
>> addressing in u-boot also.
>> This would be based on the driver, We can get the data that whether the
>> controller supports 4-byte or not from the driver level(through slave
>> struct) and enable 4 byte addressing here based on that.
>>
>
> That is a long way, and I don't think it is necessary for U-Boot. The U-Boot
> work well using BAR to address more than 16MiB flash.
> This patch focus on the address mode issue when warm boot up base on the BAR
> address mode.

Please correct me if I'm wrong, but AFAIU this BAR thing 
(CONFIG_SPI_FLASH_BAR) doesn't support to address e.g. a 64MiB SPI flash 
contiguously. Only 16MiB areas. So for example its not possible to put 
UBI/UBIFS in such a big partition.

I have to support Siva here. We really should try to support this 4-byte 
mode correctly. This can't be too hard.

Thanks,
Stefan

  reply	other threads:[~2015-08-13 11:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  6:18 [U-Boot] [PATCH V6] sf: Turn SPI flash chip into 3-Byte address mode Zhiqiang Hou
2015-08-13  9:17 ` Siva Durga Prasad Paladugu
2015-08-13 10:50   ` Hou Zhiqiang
2015-08-13 11:21     ` Stefan Roese [this message]
2015-08-13 11:27       ` Siva Durga Prasad Paladugu
2015-08-13 11:45         ` Jagan Teki
2015-08-13 11:53           ` Stefan Roese
2015-08-17  8:07             ` Jagan Teki
2015-08-13 12:48           ` Siva Durga Prasad Paladugu
2015-08-14  4:07             ` Hou Zhiqiang
2015-08-14  4:44               ` Siva Durga Prasad Paladugu
2015-08-17  8:13             ` Jagan Teki
2015-08-17  8:56               ` Siva Durga Prasad Paladugu
2015-08-17  9:12                 ` Jagan Teki
2015-08-17  9:14                   ` Siva Durga Prasad Paladugu
2015-08-17  9:21                     ` Jagan Teki
2015-08-14  4:55 ` Siva Durga Prasad Paladugu
2015-08-14 10:01   ` Hou Zhiqiang
2015-08-19 12:26   ` Hou Zhiqiang
2016-01-27  5:47     ` Zhiqiang Hou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55CC7DA1.1030605@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox