Re: [linux-sunxi] [PATCH 3.4 0/4] Various fixes to make linux-sunxi work with new u-boot
On 15 March 2015 at 12:12, Paul Kocialkowski cont...@paulk.fr wrote: Le mardi 24 février 2015 à 11:58 +0200, Siarhei Siamashka a écrit : On Sat, 21 Feb 2015 16:47:20 +0100 Hans de Goede hdego...@redhat.com wrote: Hi all, Newer u-boot versions may chose a different (better) PLL6 / PLL5 setting and/or different voltage settings. Unfortunately the old linux-sunxi-3.4 kernels have a number of hardcoded assumptions about PLL5 speed, and in some cases override the bootloader chosen PLL6 / voltages in a bad way. This patch series fixes this and is intended for the sunxi-3.4 branch. The first 2 patches are already in sunxi-3.4/staging, but they should really also be added to the sunxi-3.4 branch. The 2 new patches should be added to both. Note that sunxi-3.4/staging currently does not work for me (on sun5i at least) (*) so these patches have only been tested on the sunxi-3.4 branch. Regards, Hans *) It does not boot at all for some reason, not a single message is printed on the serial console after u-boot has loaded the kernel. I'm afraid I do not have the time to investigate this. Thanks. I will allocate the next few days of my time on checking what's up with sunxi-3.4 and maybe we can make the final graduation release for it. Any news on that front? I have been trying to boot sunxi-3.4 on sun7i/A20 using upstream U-Boot, with no success. I tried the current sunxi-3.4 branch and stage/sunxi-3.4, with and without these patches. Hi Paul, Pinged you on irc. I've been booting stage/sunxi-3.4 with mainline over fel using this script and boot.cmd http://pastebin.com/EneW2jgA http://pastebin.com/BfCUVAgB I will try sticking it on an sdcard unfortunately at the moment all my serial to usb converters seem dead so I've got no way of getting a log. Good luck, CK It never prints anything on serial. On the other hand, I was able to boot mainline Linux (3.19) just fine. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/ -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH 3.4 0/4] Various fixes to make linux-sunxi work with new u-boot
On 15 March 2015 at 12:23, Code Kipper codekip...@gmail.com wrote: On 15 March 2015 at 12:12, Paul Kocialkowski cont...@paulk.fr wrote: Le mardi 24 février 2015 à 11:58 +0200, Siarhei Siamashka a écrit : On Sat, 21 Feb 2015 16:47:20 +0100 Hans de Goede hdego...@redhat.com wrote: Hi all, Newer u-boot versions may chose a different (better) PLL6 / PLL5 setting and/or different voltage settings. Unfortunately the old linux-sunxi-3.4 kernels have a number of hardcoded assumptions about PLL5 speed, and in some cases override the bootloader chosen PLL6 / voltages in a bad way. This patch series fixes this and is intended for the sunxi-3.4 branch. The first 2 patches are already in sunxi-3.4/staging, but they should really also be added to the sunxi-3.4 branch. The 2 new patches should be added to both. Note that sunxi-3.4/staging currently does not work for me (on sun5i at least) (*) so these patches have only been tested on the sunxi-3.4 branch. Regards, Hans *) It does not boot at all for some reason, not a single message is printed on the serial console after u-boot has loaded the kernel. I'm afraid I do not have the time to investigate this. Thanks. I will allocate the next few days of my time on checking what's up with sunxi-3.4 and maybe we can make the final graduation release for it. Any news on that front? I have been trying to boot sunxi-3.4 on sun7i/A20 using upstream U-Boot, with no success. I tried the current sunxi-3.4 branch and stage/sunxi-3.4, with and without these patches. Hi Paul, Pinged you on irc. I've been booting stage/sunxi-3.4 with mainline over fel using this script and boot.cmd http://pastebin.com/EneW2jgA http://pastebin.com/BfCUVAgB I will try sticking it on an sdcard unfortunately at the moment all my serial to usb converters seem dead so I've got no way of getting a log. Good luck, CK Oopsforgot to add that needed to set legacy kernel in u-boot. CK It never prints anything on serial. On the other hand, I was able to boot mainline Linux (3.19) just fine. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/ -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH 3.4 0/4] Various fixes to make linux-sunxi work with new u-boot
Le dimanche 15 mars 2015 à 12:25 +0100, Code Kipper a écrit : On 15 March 2015 at 12:23, Code Kipper codekip...@gmail.com wrote: On 15 March 2015 at 12:12, Paul Kocialkowski cont...@paulk.fr wrote: Le mardi 24 février 2015 à 11:58 +0200, Siarhei Siamashka a écrit : On Sat, 21 Feb 2015 16:47:20 +0100 Hans de Goede hdego...@redhat.com wrote: Hi all, Newer u-boot versions may chose a different (better) PLL6 / PLL5 setting and/or different voltage settings. Unfortunately the old linux-sunxi-3.4 kernels have a number of hardcoded assumptions about PLL5 speed, and in some cases override the bootloader chosen PLL6 / voltages in a bad way. This patch series fixes this and is intended for the sunxi-3.4 branch. The first 2 patches are already in sunxi-3.4/staging, but they should really also be added to the sunxi-3.4 branch. The 2 new patches should be added to both. Note that sunxi-3.4/staging currently does not work for me (on sun5i at least) (*) so these patches have only been tested on the sunxi-3.4 branch. Regards, Hans *) It does not boot at all for some reason, not a single message is printed on the serial console after u-boot has loaded the kernel. I'm afraid I do not have the time to investigate this. Thanks. I will allocate the next few days of my time on checking what's up with sunxi-3.4 and maybe we can make the final graduation release for it. Any news on that front? I have been trying to boot sunxi-3.4 on sun7i/A20 using upstream U-Boot, with no success. I tried the current sunxi-3.4 branch and stage/sunxi-3.4, with and without these patches. Hi Paul, Pinged you on irc. I've been booting stage/sunxi-3.4 with mainline over fel using this script and boot.cmd http://pastebin.com/EneW2jgA http://pastebin.com/BfCUVAgB I will try sticking it on an sdcard unfortunately at the moment all my serial to usb converters seem dead so I've got no way of getting a log. Good luck, CK Oopsforgot to add that needed to set legacy kernel in u-boot. CK Well, I did include the patches you linked to, enabled compat for old kernels in U-Boot but it still didn't do. I'll try again in a few days. It never prints anything on serial. On the other hand, I was able to boot mainline Linux (3.19) just fine. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/ -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
[linux-sunxi] [PATCH 3.4 1/3] drm.h: Fix DRM compilation with bare-metal toolchain.
From: Paul Sokolovsky paul.sokolov...@linaro.org An ifdef in drm.h expects to be compiled with full-fledged Linux toolchain, but it's common to compile kernel with just bare-metal toolchain which doesn't define __linux__. So, also add __KERNEL__ check. Signed-off-by: Paul Sokolovsky paul.sokolov...@linaro.org Signed-off-by: Dave Airlie airl...@redhat.com --- include/drm/drm.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm.h b/include/drm/drm.h index 64ff02d..9a30c72 100644 --- a/include/drm/drm.h +++ b/include/drm/drm.h @@ -36,7 +36,7 @@ #ifndef _DRM_H_ #define _DRM_H_ -#if defined(__linux__) +#if defined(__KERNEL__) || defined(__linux__) #include linux/types.h #include asm/ioctl.h -- 1.7.9.5 -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] [PATCH 3.4 3/3] serial: 8250_sunxi: UART port selection
Signed-off-by: Paul Kocialkowski cont...@paulk.fr
---
drivers/tty/serial/8250/8250_sunxi.c | 22 --
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_sunxi.c
b/drivers/tty/serial/8250/8250_sunxi.c
index 25fdcff..1eb7927 100644
--- a/drivers/tty/serial/8250/8250_sunxi.c
+++ b/drivers/tty/serial/8250/8250_sunxi.c
@@ -335,7 +335,9 @@ static int __init sw_serial_init(void)
int ret;
int i, max = sw_serial_get_max_ports();
int used = 0;
+ int port = 0;
char uart_para[16];
+ unsigned int id = 0;
uart_used = 0;
for (i = 0; i max; i++, used = 0) {
@@ -345,10 +347,26 @@ static int __init sw_serial_init(void)
ret = script_parser_fetch(uart_para, uart_used, used,
sizeof(int));
if (ret)
pr_err(failed to get uart%d's used information\n, i);
- pr_debug(uart:%d used:%d\n, i, used);
+
+ port = sw_uart_dev[i].id;
+
+ ret = script_parser_fetch(uart_para, uart_port, port,
sizeof(int));
+ if (ret)
+ pr_err(failed to get uart%d's port information\n, i);
+
+ pr_debug(uart:%d used:%d port:%d\n, i, used, port);
+
if (used) {
uart_used |= 1 i;
- platform_device_register(sw_uart_dev[i]);
+
+ if ((id (1 port)) == 0) {
+ sw_uart_dev[i].id = port;
+ id |= (1 port);
+
+ platform_device_register(sw_uart_dev[i]);
+ } else {
+ pr_err(failed to set uart%d's port
(duplicate)\n, i);
+ }
}
}
--
1.7.9.5
--
You received this message because you are subscribed to the Google Groups
linux-sunxi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] [PATCH 3.4 2/3] sunxi_nand: 32 sectors per page and 64 bit sector bitmap support
Signed-off-by: Paul Kocialkowski cont...@paulk.fr
---
drivers/block/sunxi_nand/src/format/nand_format.c | 16 ++---
.../block/sunxi_nand/src/include/nand_drv_cfg.h|4 +-
drivers/block/sunxi_nand/src/include/nand_logic.h |4 +-
drivers/block/sunxi_nand/src/include/nand_physic.h |4 +-
drivers/block/sunxi_nand/src/include/nand_simple.h |8 +--
drivers/block/sunxi_nand/src/include/nand_type.h | 70 ++--
drivers/block/sunxi_nand/src/logic/logic_cache.c | 56 +---
drivers/block/sunxi_nand/src/logic/logic_ctl.c | 50 --
drivers/block/sunxi_nand/src/logic/mapping.c |4 +-
drivers/block/sunxi_nand/src/physic/nand_phy.c | 16 ++---
.../block/sunxi_nand/src/physic/nand_simple_r.c|2 +-
.../block/sunxi_nand/src/physic/nand_simple_w.c|6 +-
12 files changed, 127 insertions(+), 113 deletions(-)
diff --git a/drivers/block/sunxi_nand/src/format/nand_format.c
b/drivers/block/sunxi_nand/src/format/nand_format.c
index fe485b5..1c6db8e 100644
--- a/drivers/block/sunxi_nand/src/format/nand_format.c
+++ b/drivers/block/sunxi_nand/src/format/nand_format.c
@@ -220,7 +220,7 @@ __s32 _CalculatePhyOpPar(struct __PhysicOpPara_t *pPhyPar,
__u32 nZone, __u32 nB
*0 read page data failed.
*/
-static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum, __u32 nPage, __u32
SectBitmap, void *pBuf, void *pSpare)
+static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum, __u32 nPage, __u64
SectBitmap, void *pBuf, void *pSpare)
{
__s32 i, result;
__u8 *tmpSrcData, *tmpDstData, *tmpSrcPtr[4], *tmpDstPtr[4];
@@ -239,7 +239,7 @@ static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum,
__u32 nPage, __u32 S
//process the pointer to spare area data
for(i=0; i2; i++)
{
-if(SectBitmap (1i))
+if(SectBitmap ((__u64)1i))
{
tmpSrcPtr[i] = FORMAT_SPARE_BUF + 4 * i;
tmpDstPtr[i] = (__u8 *)pSpare + 4 * i;
@@ -252,7 +252,7 @@ static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum,
__u32 nPage, __u32 S
for(i=0; i2; i++)
{
-if(SectBitmap (1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
+if(SectBitmap ((__u64)1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
{
tmpSrcPtr[i+2] = LML_SPARE_BUF + 4 * (i +
SECTOR_CNT_OF_SINGLE_PAGE);
tmpDstPtr[i+2] = (__u8 *)pSpare + 8 + 4 * i;
@@ -330,7 +330,7 @@ static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum,
__u32 nPage, __u32 S
*0 write page data failed.
*/
-static __s32 _VirtualPageWrite(__u32 nDieNum, __u32 nBlkNum, __u32 nPage,
__u32 SectBitmap, void *pBuf, void *pSpare)
+static __s32 _VirtualPageWrite(__u32 nDieNum, __u32 nBlkNum, __u32 nPage,
__u64 SectBitmap, void *pBuf, void *pSpare)
{
__s32 i, result;
__u8 *tmpSrcData, *tmpDstData, *tmpSrcPtr[4], *tmpDstPtr[4];
@@ -350,7 +350,7 @@ static __s32 _VirtualPageWrite(__u32 nDieNum, __u32
nBlkNum, __u32 nPage, __u32
//process the pointer to spare area data
for(i=0; i2; i++)
{
-if(SectBitmap (1i))
+if(SectBitmap ((__u64)1i))
{
tmpSrcPtr[i] = (__u8 *)pSpare + 4 * i;
tmpDstPtr[i] = FORMAT_SPARE_BUF + 4 * i;
@@ -363,7 +363,7 @@ static __s32 _VirtualPageWrite(__u32 nDieNum, __u32
nBlkNum, __u32 nPage, __u32
for(i=0; i2; i++)
{
-if(SectBitmap (1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
+if(SectBitmap ((__u64)1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
{
tmpSrcPtr[i+2] = (__u8 *)pSpare + 8 + 4 * i;
tmpDstPtr[i+2] = LML_SPARE_BUF + 4 * (i +
SECTOR_CNT_OF_SINGLE_PAGE);
@@ -923,7 +923,7 @@ static __s32 _GetBlkLogicInfo(struct __ScanDieInfo_t
*pDieInfo)
__s32 i;
__s16 tmpPageNum[4];
__u16 tmpLogicInfo;
-__u32 spare_bitmap;
+__u64 spare_bitmap;
struct __NandUserData_t tmpSpare[2];
@@ -980,7 +980,7 @@ static __s32 _GetBlkLogicInfo(struct __ScanDieInfo_t
*pDieInfo)
//calculate the number of the page in the super block to get
spare data
tmpPage = tmpPageNum[i] * INTERLEAVE_BANK_CNT + tmpBnkNum;
//_VirtualPageRead(pDieInfo-nDie, tmpBlkNum, tmpPage,
LOGIC_INFO_BITMAP, FORMAT_PAGE_BUF, (void *)tmpSpare);
-spare_bitmap = (SUPPORT_MULTI_PROGRAM ? (0x3 | (0x3
SECTOR_CNT_OF_SINGLE_PAGE)) : 0x3);
+spare_bitmap = (SUPPORT_MULTI_PROGRAM ? ((__u64)0x3 |
((__u64)0x3 SECTOR_CNT_OF_SINGLE_PAGE)) : (__u64)0x3);
_VirtualPageRead(pDieInfo-nDie, tmpBlkNum, tmpPage,
Re: [linux-sunxi] Re: What open source community is this?
On Sun, Mar 15, 2015 at 06:12:10PM +0200, Simos Xenitellis wrote: On Sun, Mar 15, 2015 at 5:56 PM, Luc Verhaegen l...@skynet.be wrote: On Sun, Mar 15, 2015 at 11:51:03PM +0800, Quink wrote: ... Luc Verhaegen. Luc, please, start your own thread. What you are doing is hijacking. Simos I will continue the original thread later on, Mr. Pot. Luc Verhaegen. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH 3.4 1/3] drm.h: Fix DRM compilation with bare-metal toolchain.
Nevermind this series, I sent v1 again instead of v2. Sorry about the confusion. Le dimanche 15 mars 2015 à 15:14 +0100, Paul Kocialkowski a écrit : From: Paul Sokolovsky paul.sokolov...@linaro.org An ifdef in drm.h expects to be compiled with full-fledged Linux toolchain, but it's common to compile kernel with just bare-metal toolchain which doesn't define __linux__. So, also add __KERNEL__ check. Signed-off-by: Paul Sokolovsky paul.sokolov...@linaro.org Signed-off-by: Dave Airlie airl...@redhat.com --- include/drm/drm.h |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm.h b/include/drm/drm.h index 64ff02d..9a30c72 100644 --- a/include/drm/drm.h +++ b/include/drm/drm.h @@ -36,7 +36,7 @@ #ifndef _DRM_H_ #define _DRM_H_ -#if defined(__linux__) +#if defined(__KERNEL__) || defined(__linux__) #include linux/types.h #include asm/ioctl.h -- 1.7.9.5 -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
[linux-sunxi] [PATCH 3.4 v2 2/3] sunxi_nand: 32 sectors per page and 64 bit sector bitmap support
Some NAND chips (e.g. Hynix H27UCG8T2B 20nm 8G as found on the Ampe A76 tablet)
require 64 bit (instead of 32 bit) variables for sector bitmap and 32 sectors
per page (instead of 16). This change apparently does not negatively affect
other NAND chips that worked fine with the previous settings.
These changes were imported from the sunxi nand driver version 0x2, 0x12 from
20130325, which is the factory version running on the Ampe A76 tablet.
Currently, the sunxi nand driver is version 0x2, 0x09, which is much older but
has many modifications on top, making it hard to just merge the new version.
Signed-off-by: Paul Kocialkowski cont...@paulk.fr
---
drivers/block/sunxi_nand/src/format/nand_format.c | 16 ++---
.../block/sunxi_nand/src/include/nand_drv_cfg.h| 4 +-
drivers/block/sunxi_nand/src/include/nand_logic.h | 4 +-
drivers/block/sunxi_nand/src/include/nand_physic.h | 4 +-
drivers/block/sunxi_nand/src/include/nand_simple.h | 8 +--
drivers/block/sunxi_nand/src/include/nand_type.h | 70 +++---
drivers/block/sunxi_nand/src/logic/logic_cache.c | 56 +
drivers/block/sunxi_nand/src/logic/logic_ctl.c | 50 +---
drivers/block/sunxi_nand/src/logic/mapping.c | 4 +-
drivers/block/sunxi_nand/src/physic/nand_phy.c | 16 ++---
.../block/sunxi_nand/src/physic/nand_simple_r.c| 2 +-
.../block/sunxi_nand/src/physic/nand_simple_w.c| 6 +-
12 files changed, 127 insertions(+), 113 deletions(-)
diff --git a/drivers/block/sunxi_nand/src/format/nand_format.c
b/drivers/block/sunxi_nand/src/format/nand_format.c
index fe485b5..1c6db8e 100644
--- a/drivers/block/sunxi_nand/src/format/nand_format.c
+++ b/drivers/block/sunxi_nand/src/format/nand_format.c
@@ -220,7 +220,7 @@ __s32 _CalculatePhyOpPar(struct __PhysicOpPara_t *pPhyPar,
__u32 nZone, __u32 nB
*0 read page data failed.
*/
-static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum, __u32 nPage, __u32
SectBitmap, void *pBuf, void *pSpare)
+static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum, __u32 nPage, __u64
SectBitmap, void *pBuf, void *pSpare)
{
__s32 i, result;
__u8 *tmpSrcData, *tmpDstData, *tmpSrcPtr[4], *tmpDstPtr[4];
@@ -239,7 +239,7 @@ static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum,
__u32 nPage, __u32 S
//process the pointer to spare area data
for(i=0; i2; i++)
{
-if(SectBitmap (1i))
+if(SectBitmap ((__u64)1i))
{
tmpSrcPtr[i] = FORMAT_SPARE_BUF + 4 * i;
tmpDstPtr[i] = (__u8 *)pSpare + 4 * i;
@@ -252,7 +252,7 @@ static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum,
__u32 nPage, __u32 S
for(i=0; i2; i++)
{
-if(SectBitmap (1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
+if(SectBitmap ((__u64)1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
{
tmpSrcPtr[i+2] = LML_SPARE_BUF + 4 * (i +
SECTOR_CNT_OF_SINGLE_PAGE);
tmpDstPtr[i+2] = (__u8 *)pSpare + 8 + 4 * i;
@@ -330,7 +330,7 @@ static __s32 _VirtualPageRead(__u32 nDieNum, __u32 nBlkNum,
__u32 nPage, __u32 S
*0 write page data failed.
*/
-static __s32 _VirtualPageWrite(__u32 nDieNum, __u32 nBlkNum, __u32 nPage,
__u32 SectBitmap, void *pBuf, void *pSpare)
+static __s32 _VirtualPageWrite(__u32 nDieNum, __u32 nBlkNum, __u32 nPage,
__u64 SectBitmap, void *pBuf, void *pSpare)
{
__s32 i, result;
__u8 *tmpSrcData, *tmpDstData, *tmpSrcPtr[4], *tmpDstPtr[4];
@@ -350,7 +350,7 @@ static __s32 _VirtualPageWrite(__u32 nDieNum, __u32
nBlkNum, __u32 nPage, __u32
//process the pointer to spare area data
for(i=0; i2; i++)
{
-if(SectBitmap (1i))
+if(SectBitmap ((__u64)1i))
{
tmpSrcPtr[i] = (__u8 *)pSpare + 4 * i;
tmpDstPtr[i] = FORMAT_SPARE_BUF + 4 * i;
@@ -363,7 +363,7 @@ static __s32 _VirtualPageWrite(__u32 nDieNum, __u32
nBlkNum, __u32 nPage, __u32
for(i=0; i2; i++)
{
-if(SectBitmap (1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
+if(SectBitmap ((__u64)1(i + SECTOR_CNT_OF_SINGLE_PAGE)))
{
tmpSrcPtr[i+2] = (__u8 *)pSpare + 8 + 4 * i;
tmpDstPtr[i+2] = LML_SPARE_BUF + 4 * (i +
SECTOR_CNT_OF_SINGLE_PAGE);
@@ -923,7 +923,7 @@ static __s32 _GetBlkLogicInfo(struct __ScanDieInfo_t
*pDieInfo)
__s32 i;
__s16 tmpPageNum[4];
__u16 tmpLogicInfo;
-__u32 spare_bitmap;
+__u64 spare_bitmap;
struct __NandUserData_t tmpSpare[2];
@@ -980,7 +980,7 @@ static __s32 _GetBlkLogicInfo(struct __ScanDieInfo_t
*pDieInfo)
[linux-sunxi] [PATCH 3.4 v2 1/3] drm.h: Fix DRM compilation with bare-metal toolchain.
From: Paul Sokolovsky paul.sokolov...@linaro.org An ifdef in drm.h expects to be compiled with full-fledged Linux toolchain, but it's common to compile kernel with just bare-metal toolchain which doesn't define __linux__. So, also add __KERNEL__ check. Signed-off-by: Paul Sokolovsky paul.sokolov...@linaro.org Signed-off-by: Dave Airlie airl...@redhat.com --- include/drm/drm.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm.h b/include/drm/drm.h index 64ff02d..9a30c72 100644 --- a/include/drm/drm.h +++ b/include/drm/drm.h @@ -36,7 +36,7 @@ #ifndef _DRM_H_ #define _DRM_H_ -#if defined(__linux__) +#if defined(__KERNEL__) || defined(__linux__) #include linux/types.h #include asm/ioctl.h -- 1.9.1 -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: What open source community is this?
Sorry Simos, I just want to invite some students in local community to join sunxi and take part in GSOC. That email has nothing to do with the CedarX. It's so sad that there are so many misunderstand. If we have more tolerant attitudes, technical discussing should not become a flashpoint, and we can be more open too. On Sat, Mar 14, 2015 at 2:14 AM, Manuel Braga mul.br...@gmail.com wrote: On Fri, 13 Mar 2015 19:31:47 +0200 Simos Xenitellis simos.li...@googlemail.com wrote: On Fri, Mar 13, 2015 at 7:11 PM, Manuel Braga mul.br...@gmail.com wrote: Hi. What open source community is this? When others decide at our back, don't say what are their plans, and ask us to help them, and then expect us to accept the result. Simos, i am repented to have answered to your private emails asking for help. I did in good fate, in the hopes that we all could collaborate (not fight) to create great software for this hardware. In that private exchange, i repeated multiple times that technical discussing should be made in public, but Simos i see nothing. And is not nice to find this. https://groups.google.com/forum/#!topic/szdiy/goBZ5nZOEbU (And no, is not a GEM driver, what is need, as i said to you, and explained forward) If this was the plan, why not present this in mailing list. Why this behavior, why this secretism, where is the open? I don't understand. Why don't you write in this mailing list, what you writed to me, and go directly to the point. Simos, one last thing. With binaries blobs, you will no get the proper driver that you wish. Fuck my life.[non-native speakers: it's an expression like what have I done to deserve this]. Also me, what we all have done to deserve all this problems caused by this video engine. Manuel, you are quoting an email that I sent to Quink BEFORE I consulted you. In that email it says I asked Manuel Braga for some input and will come back to you. That email shows my BEFORE knowledge. In that email I suggested to Quink to try for GSOC because his G+ profile mentions that he is either a Uni student or a recent graduate (so his colleagues might find it interesting). Odd, in our private exchange, i got the impression that you told me that he(Quink) was someone else. Maybe you and Quink should explain better, who is who and what do are expecting from the rest of us. As i asked you to do, in our private exchange. (By the way, i don't know how GSOC handles binary globs) He should not have forwarded my email (it's etiquette not to forward private mails) but anyway, I do not hold grudges. @Quink: We are still good. What I see here is that you have been influenced by the negative vibes and interpreted that mail in the most negative/wrong way. Is not that email. What is negative here is the secretism floating around. And this is not healthy for an supposed open source community. Simos And i repeat again. Why don't you write in this mailing list, what you wrote to me, and go directly to the point. The others also have the right to know, and i don't see what is wrong with its content, that should not be public. -- Manuel Braga -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: What open source community is this?
On Sun, Mar 15, 2015 at 5:56 PM, Luc Verhaegen l...@skynet.be wrote: On Sun, Mar 15, 2015 at 11:51:03PM +0800, Quink wrote: ... Luc Verhaegen. Luc, please, start your own thread. What you are doing is hijacking. Simos -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH 3.4 0/4] Various fixes to make linux-sunxi work with new u-boot
On Sun, 15 Mar 2015 12:12:00 +0100 Paul Kocialkowski cont...@paulk.fr wrote: Le mardi 24 février 2015 à 11:58 +0200, Siarhei Siamashka a écrit : On Sat, 21 Feb 2015 16:47:20 +0100 Hans de Goede hdego...@redhat.com wrote: Hi all, Newer u-boot versions may chose a different (better) PLL6 / PLL5 setting and/or different voltage settings. Unfortunately the old linux-sunxi-3.4 kernels have a number of hardcoded assumptions about PLL5 speed, and in some cases override the bootloader chosen PLL6 / voltages in a bad way. This patch series fixes this and is intended for the sunxi-3.4 branch. The first 2 patches are already in sunxi-3.4/staging, but they should really also be added to the sunxi-3.4 branch. The 2 new patches should be added to both. Note that sunxi-3.4/staging currently does not work for me (on sun5i at least) (*) so these patches have only been tested on the sunxi-3.4 branch. Regards, Hans *) It does not boot at all for some reason, not a single message is printed on the serial console after u-boot has loaded the kernel. I'm afraid I do not have the time to investigate this. Thanks. I will allocate the next few days of my time on checking what's up with sunxi-3.4 and maybe we can make the final graduation release for it. Any news on that front? Thanks for reminding. Well, the news is that I could not reproduce the alleged sun5i problem with the stage/sunxi-3.4 branch on my A13-OLinuXino-Micro board. Which obviously means that I can't debug it. Combined with Tsvetan's lack of any sign of response or any indications that anyone else could be interested, I don't feel very much motivated to do the communication part of the job, which is required to clarify the status of these 3.4 branches and move them forward. I have been trying to boot sunxi-3.4 on sun7i/A20 using upstream U-Boot, with no success. I tried the current sunxi-3.4 branch and stage/sunxi-3.4, with and without these patches. It never prints anything on serial. Most likely you are missing the setenv bootm_boot_mode sec line in your boot.cmd (otherwise the PSCI code in u-boot drops the CPU into the non-secure mode and the sunxi-3.4 kernel can't handle it). The documentation in the wiki about the mainline u-boot is in a pretty much bad shape, but at least this should be covered: http://linux-sunxi.org/Mainline_U-boot#Boot Alternatively, there is the old kernel compatibility mode in u-boot, which can be selected in menuconfig. It should work with any old sunxi-3.4 kernels. On the other hand, I was able to boot mainline Linux (3.19) just fine. Right. That's what everyone should be using now. -- Best regards, Siarhei Siamashka -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH 3.4 0/4] Various fixes to make linux-sunxi work with new u-boot
Le dimanche 15 mars 2015 à 14:10 +0200, Siarhei Siamashka a écrit : On Sun, 15 Mar 2015 12:12:00 +0100 Paul Kocialkowski cont...@paulk.fr wrote: Le mardi 24 février 2015 à 11:58 +0200, Siarhei Siamashka a écrit : On Sat, 21 Feb 2015 16:47:20 +0100 Hans de Goede hdego...@redhat.com wrote: Hi all, Newer u-boot versions may chose a different (better) PLL6 / PLL5 setting and/or different voltage settings. Unfortunately the old linux-sunxi-3.4 kernels have a number of hardcoded assumptions about PLL5 speed, and in some cases override the bootloader chosen PLL6 / voltages in a bad way. This patch series fixes this and is intended for the sunxi-3.4 branch. The first 2 patches are already in sunxi-3.4/staging, but they should really also be added to the sunxi-3.4 branch. The 2 new patches should be added to both. Note that sunxi-3.4/staging currently does not work for me (on sun5i at least) (*) so these patches have only been tested on the sunxi-3.4 branch. Regards, Hans *) It does not boot at all for some reason, not a single message is printed on the serial console after u-boot has loaded the kernel. I'm afraid I do not have the time to investigate this. Thanks. I will allocate the next few days of my time on checking what's up with sunxi-3.4 and maybe we can make the final graduation release for it. Any news on that front? Thanks for reminding. Well, the news is that I could not reproduce the alleged sun5i problem with the stage/sunxi-3.4 branch on my A13-OLinuXino-Micro board. Which obviously means that I can't debug it. Well, last time I checked, I didn't experience any particular problem with mainline U-Boot and sunxi-3.4 on sun5i/A13 but I probably lack context on this. Combined with Tsvetan's lack of any sign of response or any indications that anyone else could be interested, I don't feel very much motivated to do the communication part of the job, which is required to clarify the status of these 3.4 branches and move them forward. Still, I would be interested in having a sunxi-3.4 branch that can actually be used on all the supported chips and devices. I have been trying to boot sunxi-3.4 on sun7i/A20 using upstream U-Boot, with no success. I tried the current sunxi-3.4 branch and stage/sunxi-3.4, with and without these patches. It never prints anything on serial. Most likely you are missing the setenv bootm_boot_mode sec line in your boot.cmd (otherwise the PSCI code in u-boot drops the CPU into the non-secure mode and the sunxi-3.4 kernel can't handle it). That could be it, I'll investigate. The documentation in the wiki about the mainline u-boot is in a pretty much bad shape, but at least this should be covered: http://linux-sunxi.org/Mainline_U-boot#Boot Alternatively, there is the old kernel compatibility mode in u-boot, which can be selected in menuconfig. It should work with any old sunxi-3.4 kernels. On the other hand, I was able to boot mainline Linux (3.19) just fine. Right. That's what everyone should be using now. Well, it doesn't fit every use case yet and I will (sadly) have to use sunxi-3.4 for Replicant, so I need something that actually works. Thanks, -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/ -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: [linux-sunxi] Re: What open source community is this?
On Sun, Mar 15, 2015 at 11:51:03PM +0800, Quink wrote: Sorry Simos, I just want to invite some students in local community to join sunxi and take part in GSOC. That email has nothing to do with the CedarX. It's so sad that there are so many misunderstand. If we have more tolerant attitudes, technical discussing should not become a flashpoint, and we can be more open too. I just found some lgpled symbols in your supposed clean binaries. I will now spend the time to irrefutably prove that Allwinner CedarX binaries are a cesspool of license violations that Allwinner has had no and still has no control over. So much for more tolerant attitudes and misunderstandings. Allwinner has absolutely no credibility left in this story. Luc Verhaegen. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] [PATCH 3.4 0/4] Various fixes to make linux-sunxi work with new u-boot
Le mardi 24 février 2015 à 11:58 +0200, Siarhei Siamashka a écrit : On Sat, 21 Feb 2015 16:47:20 +0100 Hans de Goede hdego...@redhat.com wrote: Hi all, Newer u-boot versions may chose a different (better) PLL6 / PLL5 setting and/or different voltage settings. Unfortunately the old linux-sunxi-3.4 kernels have a number of hardcoded assumptions about PLL5 speed, and in some cases override the bootloader chosen PLL6 / voltages in a bad way. This patch series fixes this and is intended for the sunxi-3.4 branch. The first 2 patches are already in sunxi-3.4/staging, but they should really also be added to the sunxi-3.4 branch. The 2 new patches should be added to both. Note that sunxi-3.4/staging currently does not work for me (on sun5i at least) (*) so these patches have only been tested on the sunxi-3.4 branch. Regards, Hans *) It does not boot at all for some reason, not a single message is printed on the serial console after u-boot has loaded the kernel. I'm afraid I do not have the time to investigate this. Thanks. I will allocate the next few days of my time on checking what's up with sunxi-3.4 and maybe we can make the final graduation release for it. Any news on that front? I have been trying to boot sunxi-3.4 on sun7i/A20 using upstream U-Boot, with no success. I tried the current sunxi-3.4 branch and stage/sunxi-3.4, with and without these patches. It never prints anything on serial. On the other hand, I was able to boot mainline Linux (3.19) just fine. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/ -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: [linux-sunxi] Re: What open source community is this?
On Sun, 15 Mar 2015 23:51:03 +0800 Quink wantl...@gmail.com wrote: Sorry Simos, I just want to invite some students in local community to join sunxi and take part in GSOC. And everyone are welcome to join sunxi. And the GSOC idea is not bad, please do invite students. That email has nothing to do with the CedarX. It's so sad that there are so many misunderstand. If we have more I agree, let's resolve this misunderstanding. Simos for whatever reason, still didn't make public what he wrote to me in our private exchange. And this is making me suspicious. Maybe you Quink, could help here. By telling, who are you?, and your connection to allwinner?, if any. What is you want to do? And, what kind of help are expected from linux-sunxi? tolerant attitudes, technical discussing should not become a flashpoint, and we can be more Your technical question that was made in your last email is unanswered because was part of an email that started with a flashpoint. Let's keep the technical discussing, separated from flashpoints. open too. Yes, let's all be open. -- Manuel Braga -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] [RFC] Serial number on sunxi devices
As far as I know, there is currently no mechanism in place to give each device a unique serial number, that would be shown in e.g. /proc/cpuinfo. This can seem not very useful, but it would be nice to have that for USB gadget drivers that make use of it (e.g. ADB on Android, fastboot, etc). This would allow having multiple sunxi devices connected at the same time. Normally, the serial number has to be figured out by the bootloader and passed to the kernel through ATAGs. In U-Boot, it is defined using get_board_serial, that is not yet implemented on sunxi. I'm interested in figuring out the best way to do this. As far as I can see, Allwinner SoCs have some e-fuses, known as SID (Security ID): http://linux-sunxi.org/SID_Register_Guide for which Oliver has written a mainline Linux driver. Those should have device-specific values, except when they are set to 0. Do you have any better idea to do this, or is there some reference that I am missing? Thanks, -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution running on several devices, a free software mobile operating system putting the emphasis on freedom and privacy/security. Website: http://www.replicant.us/ Blog: http://blog.replicant.us/ Wiki/tracker/forums: http://redmine.replicant.us/ -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: [linux-sunxi] Re: What open source community is this?
I'm an employee of allwinner, and I joined this mailing list before joined the company. I speak for myself here. I have a Cubieboard2 (I bought it to do real-time vibration control as a graduate students.) runing Linux and want to playback video on that, and I saw some people have the same idea too. I want to find a workable solution, that's all. So, if we can get all of the source code from allwinner, and work out the complete open source solution, that is the best. If we can't, I want to find out just a workable solution. The graphic card AMD radeon 545v didn't work well with open source driver until Linux kernel 3.13. Before that, I have to use my laptop too, with AMD private driver. It seems that no one takes the cedar binaries as a solution, no matter whether it has been cleaned of not. If Cedrus is the only workable solution, I will try to figure out how to contribute to this project. On Mon, Mar 16, 2015 at 5:03 AM, Manuel Braga mul.br...@gmail.com wrote: On Sun, 15 Mar 2015 23:51:03 +0800 Quink wantl...@gmail.com wrote: Sorry Simos, I just want to invite some students in local community to join sunxi and take part in GSOC. And everyone are welcome to join sunxi. And the GSOC idea is not bad, please do invite students. That email has nothing to do with the CedarX. It's so sad that there are so many misunderstand. If we have more I agree, let's resolve this misunderstanding. Simos for whatever reason, still didn't make public what he wrote to me in our private exchange. And this is making me suspicious. Maybe you Quink, could help here. By telling, who are you?, and your connection to allwinner?, if any. What is you want to do? And, what kind of help are expected from linux-sunxi? tolerant attitudes, technical discussing should not become a flashpoint, and we can be more Your technical question that was made in your last email is unanswered because was part of an email that started with a flashpoint. Let's keep the technical discussing, separated from flashpoints. open too. Yes, let's all be open. -- Manuel Braga -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Annoucement about Allwinner's CedarX Software Licensing
To better support media codec framework and media player applications, Allwinner has published the newest version of CedarX (Media Codec framework) to github, at this url: https://github.com/allwinner-zh/media-codec Recently, there have been some questions about CedarX's software licensing. To clear up any misconceptions about Allwinner's support and respect for the open source community, the CedarX media codec framework is now released with full open source code under the LGPL license. Everyone can get the complete source code from github: https://github.com/allwinner-zh/media-codec. With this, we believe Allwinner's CedarX license is fully compiliant and resolves concerns from the community. On another positive note, with the release of this framework developers can now support media encode and decode with Allwinner's media libraries (hardware module implemented in user space), or the third media library. We believe this is an important benefit for developers who want more freedom to write code for their projects. We thank the community for working together with us to expand our open source support. If there are any questions or further requests please don't hesitate to reach out to us via direct channels or via existing mailing lists. We'll do our best to help out. Best Regards, ke...@allwinnertech.com NOTICE: This e-mail and any included attachments are intended only for the sole use of named and intended recipient (s) only. If you are the named and intended recipient, please note that the information contained in this email and its embedded files are confidential and privileged. If you are neither the intended nor named recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. Please reply to the sender and destroy the original message and all your records of this message (whether electronic or otherwise). Furthermore, you should not disclose to any other person, use, copy or disseminate the contents of this e-mail and/or the documents accompanying it. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
