Re: [PATCH 27/47] Update CRISv10 rescue head.s
On Thu, Dec 06, 2007 at 05:58:04AM -0800, David Miller wrote: > From: Jesper Nilsson <[EMAIL PROTECTED]> > Date: Fri, 30 Nov 2007 16:13:29 +0100 >^^^ > > Any particular reason for the 6 day long delay in these mails going > out or is your clock simply wrong? > As co-postmaster, I am noticing that your postings are bouncing at a > lot of sites because of this. There are several that impose things > like 96-hour-old limits on date fields in received mails. Sorry, this is not intended. I have no idea why the date was set to a random value, but it was certainly not my intention. I did run a script to send the mails, but it's not clear to me why the date would be screwed up. Another lesson to be learned I guess, back to manual submission. /^JN - Jesper Nilsson -- Jesper Nilsson -- [EMAIL PROTECTED] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 27/47] Update CRISv10 rescue head.s
From: Jesper Nilsson <[EMAIL PROTECTED]> Date: Fri, 30 Nov 2007 16:13:29 +0100 ^^^ Any particular reason for the 6 day long delay in these mails going out or is your clock simply wrong? As co-postmaster, I am noticing that your postings are bouncing at a lot of sites because of this. There are several that impose things like 96-hour-old limits on date fields in received mails. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 27/47] Update CRISv10 rescue head.s
- Correct whitespace problems. - Add ifdef for ETRAX_AXISFLASHMAP to avoid compile error when not set. Signed-off-by: Jesper Nilsson <[EMAIL PROTECTED]> --- arch/cris/arch-v10/boot/rescue/head.S | 117 + 1 files changed, 61 insertions(+), 56 deletions(-) diff --git a/arch/cris/arch-v10/boot/rescue/head.S b/arch/cris/arch-v10/boot/rescue/head.S index f223cc0..cf644e2 100644 --- a/arch/cris/arch-v10/boot/rescue/head.S +++ b/arch/cris/arch-v10/boot/rescue/head.S @@ -1,5 +1,4 @@ -/* $Id: head.S,v 1.7 2005/03/07 12:11:06 starvik Exp $ - * +/* * Rescue code, made to reside at the beginning of the * flash-memory. when it starts, it checks a partition * table at the first sector after the rescue sector. @@ -23,20 +22,20 @@ * Partition table format: * * Code transparency: - * + * * 2 bytes[opcode 'nop'] * 2 bytes[opcode 'di'] * 4 bytes[opcode 'ba ', 8-bit or 16-bit version] * 2 bytes[opcode 'nop', delay slot] * - * Table validation (at +10): - * + * Table validation (at +10): + * * 2 bytes[magic/version word for partitiontable - 0xef, 0xbe] * 2 bytes[length of all entries plus the end marker] * 4 bytes[checksum for the partitiontable itself] * - * Entries, each with the following format, last has offset -1: - * + * Entries, each with the following format, last has offset -1: + * *4 bytes[offset in bytes, from start of flash] *4 bytes[length in bytes of partition] *4 bytes[checksum, simple longword sum] @@ -47,9 +46,9 @@ * End marker * *4 bytes[-1] - * + * * 10 bytes[0, padding] - * + * * Bit 0 in flags signifies RW or RO. The rescue code only bothers * to check the checksum for RO partitions, since the others will * change their data without updating the checksums. A 1 in bit 0 @@ -59,16 +58,18 @@ * * During the wait for serial input, the status LED will flash so the * user knows something went wrong. - * - * Copyright (C) 1999, 2000, 2001, 2002, 2003 Axis Communications AB + * + * Copyright (C) 1999-2007 Axis Communications AB */ +#ifdef CONFIG_ETRAX_AXISFLASHMAP + #define ASSEMBLER_MACROS_ONLY #include ;; The partitiontable is looked for at the first sector after the boot ;; sector. Sector size is 65536 bytes in all flashes we use. - + #define PTABLE_START CONFIG_ETRAX_PTABLE_SECTOR #define PTABLE_MAGIC 0xbeef @@ -78,7 +79,7 @@ ;; having setup the DRAM etc). It is the same length as the on-chip ;; ROM loads, so the same host loader can be used to load a rescued ;; product as well as one booted through the Etrax serial boot code. - + #define CODE_START 0x4000 #define CODE_LENGTH 784 @@ -102,7 +103,7 @@ #define SERRECC R_SERIAL2_REC_CTRL #define SERRDAT R_SERIAL2_REC_DATA #define SERSTAT R_SERIAL2_STATUS -#endif +#endif #ifdef CONFIG_ETRAX_RESCUE_SER3 #define SERXOFF R_SERIAL3_XOFF #define SERBAUD R_SERIAL3_BAUD @@ -115,60 +116,61 @@ #define RAM_INIT_MAGIC 0x56902387 .text - + ;; This is the entry point of the rescue code ;; 0x8000 if loaded in flash (as it should be) - ;; since etrax actually starts at address 2 when booting from flash, we + ;; Since etrax actually starts at address 2 when booting from flash, we ;; put a nop (2 bytes) here first so we dont accidentally skip the di - nop + nop di jumpin_cache; enter cached area instead in_cache: - ;; first put a jump test to give a possibility of upgrading the rescue code - ;; without erasing/reflashing the sector. we put a longword of -1 here and if - ;; it is not -1, we jump using the value as jump target. since we can always - ;; change 1's to 0's without erasing the sector, it is possible to add new + ;; First put a jump test to give a possibility of upgrading the + ;; rescue code without erasing/reflashing the sector. + ;; We put a longword of -1 here and if it is not -1, we jump using + ;; the value as jump target. Since we can always change 1's to 0's + ;; without erasing the sector, it is possible to add new ;; code after this and altering the jumptarget in an upgrade. jtcd: move.d [jumptarget], $r0 cmp.d 0x, $r0 beq no_newjump nop - + jump[$r0] -jumptarget: +jumptarget: .dword 0x ; can be overwritten later to insert new code - + no_newjump: -#ifdef CONFIG_ETRAX_ETHERNET +#ifdef CONFIG_ETRAX_ETHERNET ;; Start MII clock to make sure it is running when tranceiver is reset move.d 0x3, $r0; enable = on, phy = mii_clk move.d $r0, [R_NETWORK_GEN_CONFIG] #endif - + ;; We need to setup the bus
[PATCH 27/47] Update CRISv10 rescue head.s
- Correct whitespace problems. - Add ifdef for ETRAX_AXISFLASHMAP to avoid compile error when not set. Signed-off-by: Jesper Nilsson [EMAIL PROTECTED] --- arch/cris/arch-v10/boot/rescue/head.S | 117 + 1 files changed, 61 insertions(+), 56 deletions(-) diff --git a/arch/cris/arch-v10/boot/rescue/head.S b/arch/cris/arch-v10/boot/rescue/head.S index f223cc0..cf644e2 100644 --- a/arch/cris/arch-v10/boot/rescue/head.S +++ b/arch/cris/arch-v10/boot/rescue/head.S @@ -1,5 +1,4 @@ -/* $Id: head.S,v 1.7 2005/03/07 12:11:06 starvik Exp $ - * +/* * Rescue code, made to reside at the beginning of the * flash-memory. when it starts, it checks a partition * table at the first sector after the rescue sector. @@ -23,20 +22,20 @@ * Partition table format: * * Code transparency: - * + * * 2 bytes[opcode 'nop'] * 2 bytes[opcode 'di'] * 4 bytes[opcode 'ba offset', 8-bit or 16-bit version] * 2 bytes[opcode 'nop', delay slot] * - * Table validation (at +10): - * + * Table validation (at +10): + * * 2 bytes[magic/version word for partitiontable - 0xef, 0xbe] * 2 bytes[length of all entries plus the end marker] * 4 bytes[checksum for the partitiontable itself] * - * Entries, each with the following format, last has offset -1: - * + * Entries, each with the following format, last has offset -1: + * *4 bytes[offset in bytes, from start of flash] *4 bytes[length in bytes of partition] *4 bytes[checksum, simple longword sum] @@ -47,9 +46,9 @@ * End marker * *4 bytes[-1] - * + * * 10 bytes[0, padding] - * + * * Bit 0 in flags signifies RW or RO. The rescue code only bothers * to check the checksum for RO partitions, since the others will * change their data without updating the checksums. A 1 in bit 0 @@ -59,16 +58,18 @@ * * During the wait for serial input, the status LED will flash so the * user knows something went wrong. - * - * Copyright (C) 1999, 2000, 2001, 2002, 2003 Axis Communications AB + * + * Copyright (C) 1999-2007 Axis Communications AB */ +#ifdef CONFIG_ETRAX_AXISFLASHMAP + #define ASSEMBLER_MACROS_ONLY #include asm/arch/sv_addr_ag.h ;; The partitiontable is looked for at the first sector after the boot ;; sector. Sector size is 65536 bytes in all flashes we use. - + #define PTABLE_START CONFIG_ETRAX_PTABLE_SECTOR #define PTABLE_MAGIC 0xbeef @@ -78,7 +79,7 @@ ;; having setup the DRAM etc). It is the same length as the on-chip ;; ROM loads, so the same host loader can be used to load a rescued ;; product as well as one booted through the Etrax serial boot code. - + #define CODE_START 0x4000 #define CODE_LENGTH 784 @@ -102,7 +103,7 @@ #define SERRECC R_SERIAL2_REC_CTRL #define SERRDAT R_SERIAL2_REC_DATA #define SERSTAT R_SERIAL2_STATUS -#endif +#endif #ifdef CONFIG_ETRAX_RESCUE_SER3 #define SERXOFF R_SERIAL3_XOFF #define SERBAUD R_SERIAL3_BAUD @@ -115,60 +116,61 @@ #define RAM_INIT_MAGIC 0x56902387 .text - + ;; This is the entry point of the rescue code ;; 0x8000 if loaded in flash (as it should be) - ;; since etrax actually starts at address 2 when booting from flash, we + ;; Since etrax actually starts at address 2 when booting from flash, we ;; put a nop (2 bytes) here first so we dont accidentally skip the di - nop + nop di jumpin_cache; enter cached area instead in_cache: - ;; first put a jump test to give a possibility of upgrading the rescue code - ;; without erasing/reflashing the sector. we put a longword of -1 here and if - ;; it is not -1, we jump using the value as jump target. since we can always - ;; change 1's to 0's without erasing the sector, it is possible to add new + ;; First put a jump test to give a possibility of upgrading the + ;; rescue code without erasing/reflashing the sector. + ;; We put a longword of -1 here and if it is not -1, we jump using + ;; the value as jump target. Since we can always change 1's to 0's + ;; without erasing the sector, it is possible to add new ;; code after this and altering the jumptarget in an upgrade. jtcd: move.d [jumptarget], $r0 cmp.d 0x, $r0 beq no_newjump nop - + jump[$r0] -jumptarget: +jumptarget: .dword 0x ; can be overwritten later to insert new code - + no_newjump: -#ifdef CONFIG_ETRAX_ETHERNET +#ifdef CONFIG_ETRAX_ETHERNET ;; Start MII clock to make sure it is running when tranceiver is reset move.d 0x3, $r0; enable = on, phy = mii_clk move.d $r0, [R_NETWORK_GEN_CONFIG] #endif - + ;; We
Re: [PATCH 27/47] Update CRISv10 rescue head.s
From: Jesper Nilsson [EMAIL PROTECTED] Date: Fri, 30 Nov 2007 16:13:29 +0100 ^^^ Any particular reason for the 6 day long delay in these mails going out or is your clock simply wrong? As co-postmaster, I am noticing that your postings are bouncing at a lot of sites because of this. There are several that impose things like 96-hour-old limits on date fields in received mails. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 27/47] Update CRISv10 rescue head.s
On Thu, Dec 06, 2007 at 05:58:04AM -0800, David Miller wrote: From: Jesper Nilsson [EMAIL PROTECTED] Date: Fri, 30 Nov 2007 16:13:29 +0100 ^^^ Any particular reason for the 6 day long delay in these mails going out or is your clock simply wrong? As co-postmaster, I am noticing that your postings are bouncing at a lot of sites because of this. There are several that impose things like 96-hour-old limits on date fields in received mails. Sorry, this is not intended. I have no idea why the date was set to a random value, but it was certainly not my intention. I did run a script to send the mails, but it's not clear to me why the date would be screwed up. Another lesson to be learned I guess, back to manual submission. /^JN - Jesper Nilsson -- Jesper Nilsson -- [EMAIL PROTECTED] -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
