lacie 5 big network v.1 please support for fvdw

lacie 5 big network v.1 please support for fvdw

Postby taetae » Mon Aug 26, 2013 9:20 am

Code: Select all
CPU : ARM926 (Rev 0)

Soc: 88F5281 D0 (DDR2)
CPU running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  32bit width
[4096kB@ffc00000] Flash:  4 MB

Other   
NIC    Gigabit Ethernet 10/100/1000 Base-TX
USB    1x USB 2 for additional storage, data import and external backups
internal HDD    supports RAID 5, RAID 5+Spare, RAID 6, RAID 10*, RAID 10+Spare, RAID 0
SATA Controller    4/5 internal SATA, 3x eSATA for additional storage, data import and external backups
Drive Capacity    2.5TB, 5TB, 7.5TB, 10TB versions. Total accessible capacity varies depending upon operating environment (typically 10–15% less). Capacity also varies depending upon RAID modes. In RAID 5/5+Spare/6, the capacity varies according to the number of disks (more capacity with 5 disks).
Fan    Ultra-quiet cooling system with self-stabilizing oil-pressure bearing technology
Kernel    Linux 2.6.22.7



I saw your firmware and it is really well done and I was wondering ... There is no way to adapt it to my nas? I do not have the need for the raid but individual disks accessible and saw that your firmware to many great things ... congratulations for the work done and SORRY FOR MY ENGLISH

I hope you will help me to make a firmware that I can use on this nas

thank you very much in advance

Gpl archive http://gpl.nas-central.org/LACIE/2big_network/
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Mon Aug 26, 2013 10:02 am

yes I think support can be added, its a nas based on orion platform, and is supported in the vanilla kernel we use as far as I know. I need to check if our kernel compiled for orion based devices includes support for it. Any idea which mach number is used by Lacie for this device ? In the past they had the habbit to use 526 for all devices, as result you need to adapt kernel source to assign right mach number.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby taetae » Mon Aug 26, 2013 10:21 am

tell me what to do and I do it ... I have close to 48 hours nos then for work I'll be out 16 days ...

tell me what I need to check and make and give you all the details you want ....

of course tell me step by step what to look for ...

tanks tanks tanks
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Re: lacie 5 big network v.1 please support for fvdw

Postby Mijzelf » Mon Aug 26, 2013 10:46 am

The mach number might be visible when you execute 'printenv' on the bootloader (u-boot) prompt.
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

Re: lacie 5 big network v.1 please support for fvdw

Postby taetae » Mon Aug 26, 2013 11:10 am

ok :

Code: Select all
baudrate=115200
loads_echo=0
ipaddr=192.168.253.251
serverip=192.168.253.250
rootpath=/mnt/ARM_FS/
ethaddr=00:d0:4b:8b:60:2b
stdin=serial
stdout=serial
stderr=serial
cpuName=926
enaDebugLed=yes
arcNumber=526
CASset=min
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
enaVFP=yes
enaWrAllo=no
enaICPref=yes
enaDCPref=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:egiga0:none
image_name=uImage
standalone=fsload 0x400000 $(image_name);setenv bootargs $(bootargs) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x400000;
disaMvPnp=no
eth1addr=00:00:00:00:51:82
overEthAddr=no
pciMode=host
usb0Mode=host
bootdelay=40
bootcmd=if lump 5; then ; else run disk_disk; fi
kernel_addr=0x400000
boot_disk10=disk ${kernel_addr} 4:6
boot_disk9=if disk ${kernel_addr} 3:6; then; else run boot_disk10; fi
boot_disk8=if disk ${kernel_addr} 2:6; then; else run boot_disk9; fi
boot_disk7=if disk ${kernel_addr} 1:6; then; else run boot_disk8; fi
boot_disk6=if disk ${kernel_addr} 0:6; then; else run boot_disk7; fi
boot_disk5=if disk ${kernel_addr} 4:A; then; else run boot_disk6; fi
boot_disk4=if disk ${kernel_addr} 3:A; then; else run boot_disk5; fi
boot_disk3=if disk ${kernel_addr} 2:A; then; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 1:A; then; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 0:A; then; else run boot_disk2; fi
disk_disk=ide reset; run boot_disk1; bootm ${kernel_addr};
ethact=egiga0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5281 productType=5Big reset=0

Environment size: 1583/4092 bytes
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Mon Aug 26, 2013 4:38 pm

so it is 526

Code: Select all
arcNumber=526


I see in the vanilla kernel in the orion git only a net2big (v1) setup file

@mijzelf would that also work for a net5big (v1) ? I guess only a trial will give the answer.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby Mijzelf » Mon Aug 26, 2013 6:18 pm

Don't know. As far as I know you have more experience with this than I have. The differences in the GPL sources are not shocking:
2Big:
Code: Select all
#if defined(CONFIG_LACIE_2BIG)

/* --- Board ID --- */
/* This is displayed by both Uboot and Linux during the boot process                                 */
/* N.B.: The name reported from U-Boot must match the exact name stored in the board's configuration */

#define DB_CUSTOMER_BOARD_NAME  "DB-88F5182-LaCie"

/* --- I2C Devices --- */
#define DB_CUSTOMER_BOARD_I2D_DEV_LIST_CNT  2
#define DB_CUSTOMER_BOARD_I2D_DEV_LIST      { 0x32, 0x50 }

/* --- Device CS --- */
/* {CS type, params, devType, devWidth}*/

#define DB_CUSTOMER_BOARD_DEVCS_LIST_CNT    1
#define DB_CUSTOMER_BOARD_DEVCS_LIST        {3, 0x8fcfffff, BOARD_DEV_NOR_FLASH, 8} /* bootCs */                   

/* --- MPP/GPP mapping --- */
/* ---
   --- Set MPPSel registers in order to map the MPP in the following way
   ---

   MPP#    |      Description     |         ID          | Purpose (values from MSB to LSP)
   ---------------------------------------------------------------------------------------------------------------
      0    |     GPP - Input      | RAID_MODE 0         | Raid mode bit 0 (cf. MPP#2)
      1    |     GPP - Input      | USB-CTL2            | Power ctrl on USB port 2: OK(1) or FAIL(0)
      2    |     GPP - Input      | RAID_MODE 1         | Raid mode bit 1 BIG(00b), SAFE(11b)
      3    |     GPP - Input      | BOARD_IDENT (0)     | HW Board ID bit 0 (cf. MPP#12)
      4    |     GPP - Input      | FAN-ON              | FAN activity : Running (1) or OFF(0)
      5    |     GPP - Input      | /FAN-FAIL           | FAN status : OK(1) or FAIL(0)
      6    |     GPP - Output     | LED_FAIL            | Front LED Red : ON(1) or OFF(0)
      7    |     GPP - Output     | PWRON_BLINKING      | Control initial Red/Blue HW blinking STOP(1), CONTINUE(0)
     8-9   |   GPP - Input/INTR   | SW_ON & SW_OFF      | Power switch : ON(01b), AUTO(00b) or OFF(10b)
      10   |     GPP - Output     | FAIL_HD1            | Red LED for HD1 : ON(1), OFF(0)
      11   |     GPP - Output     | FAIL_HD0            | Red LED for HD0 : ON(1), OFF(0)
      12   |     GPP - Input      | BOARD_IDENT (1)     | HW Board ID bit 1 (00b)
      13   |     GPP - Output     | CDE_LED_HD1         | HD 1 LED blink Ctrl: ON(0) or OFF(1) -> linked to status of SATA 1 activity
      14   |     SATA 0 active    | ACT_HD0             | HD 0 activity (Active low)
      15   |     SATA 1 active    | ACT_HD1             | HD 1 activity (Active low)
      16   |     GPP - Output     | CDE_LED             | Front LED Blue Ctrl: ON(1) or OFF(0)
      17   |     GPP - Output     | CDE_LED_HD0         | HD 0 LED blink Ctrl: ON(0) or OFF(1) -> linked to status of SATA 1 activity
      18   |   GPP - Input/INTR   | PB                  | Front button: PUSHED(1) or RELEASED(0)
      19   |     GPP - Output     | REQ_PWR_HD0         | HD (0 & 1) power command : ON(1) or OFF(0)
    20-21  |      Clock PCI       | clock PCI           | N/A
      22   |     GPP - Input      | USB-CTL1            | Power ctrl on USB port 1: OK(1) or FAIL(0)
      23   |     GPP - Input      | PWR_HD0             | Power state of HD0 : ON(1), OFF(0)
      24   |     GPP - Output     | SHUTDOWN_REQ        | HW Power control: DISABLE(0) or ENABLE(1)
      25   |     GPP - Input      | PWR_HD1             | Power state of HD1 : ON(1), OFF(0)
   ---
   -----------------------------------------------------------------------
   ---
*/
#define DB_CUSTOMER_BOARD_MPP0_7    0x00000003  /*|                   */
#define DB_CUSTOMER_BOARD_MPP8_15   0x55000000  /*|-> MPP/GPP mapping */
#define DB_CUSTOMER_BOARD_MPP16_23  0x00005555  /*|                   */
#define DB_CUSTOMER_BOARD_MPP_DEV   N_A
#define DB_CUSTOMER_BOARD_GPP_OE    0x02F4133F  /* Bit mask for GPP direction (1-In, 0-Out) */
                                                /* GPP#:   22 2222 1111 1111 11             */
                                                /*       --54 3210 9876 5432 1098 7654 3210 */
                                                /* MASK: 0010 1111 0100 0001 0011 0011 1111 */
                                                /* HEX:    2    F    4    1    3    3    F  */

#define DB_CUSTOMER_BOARD_GPP_VAL   0x00090080  /* Bit mask for the value Output GPP        */
                                                /* GPP#:   22 2222 1111 1111 11             */
                                                /*       --54 3210 9876 5432 1098 7654 3210 */
                                                /* MASK: 0000 0000 1001 0000 0000 1000 0000 */
                                                /* HEX:    0    0    9    0    0    8    0  */



//#define DB_CUSTOMER_BOARD_GPP_VAL   0x00080000   /* Bit mask for the value Output GPP        */
                                                /* GPP#:   22 2222 1111 1111 11             */
                                                /*       --54 3210 9876 5432 1098 7654 3210 */
                                                /* MASK: 1110 1111 0100 0001 0011 0011 1111 */
                                                /* MASK: 0001 0000 1000 0000 0000 0000 0000 */
                                                /* HEX:    0    0    8    0    0    0    0  */

#define DB_CUSTOMER_BOARD_GPP_POL   N_A

#define LACIE_BOARD_MPP8_15_SATA0_MASK  0x0F000000
#define LACIE_BOARD_MPP8_15_SATA1_MASK  0xF0000000
#define LACIE_BOARD_MPP8_15_SATA_MASK   (LACIE_BOARD_MPP8_15_SATA0_MASK | LACIE_BOARD_MPP8_15_SATA1_MASK)

#define LACIE_BOARD_MPP8_15_SATA0       0x05000000
#define LACIE_BOARD_MPP8_15_SATA1       0x50000000
#define LACIE_BOARD_MPP8_15_SATA        (LACIE_BOARD_MPP8_15_SATA0 | LACIE_BOARD_MPP8_15_SATA1)
#define LACIE_BOARD_MPP8_15_NO_SATA0    0x00000000
#define LACIE_BOARD_MPP8_15_NO_SATA1    0x00000000
#define LACIE_BOARD_MPP8_15_NO_SATA     0x00000000

/* --- GPP IN devices map --- */

#define LACIE_HW_BOARD_ID_GPP       (MV_GPP3 | MV_GPP12)
#define LACIE_FAN_ACTIVITY_GPP      MV_GPP4
#define LACIE_FAN_STATUS_GPP        MV_GPP5
#define LACIE_POWER_SWITCH_ON_GPP   MV_GPP8
#define LACIE_POWER_SWITCH_OFF_GPP  MV_GPP9
#define LACIE_POWER_SWITCH_GPP      (LACIE_POWER_SWITCH_ON_GPP | LACIE_POWER_SWITCH_OFF_GPP)
#define LACIE_PUSH_BUTTON_GPP       MV_GPP18
#define LACIE_USB_POWER_STATUS_GPP  (MV_GPP1 | MV_GPP22)

/* --- GPP OUT devices map --- */

#define LACIE_HDD_POWER_CTRL_GPP        MV_GPP19
#define LACIE_HDD_POWER_STATUS_GPP      (MV_GPP23 | MV_GPP25)
#define LACIE_FRONT_RED_LED_CTRL_GPP    MV_GPP6
#define LACIE_HD0_ACTIVITY_CTRL_GPP     MV_GPP14
#define LACIE_HD1_ACTIVITY_CTRL_GPP     MV_GPP15
#define LACIE_FRONT_LED_BLINK_CTRL_GPP  MV_GPP7
#define LACIE_FRONT_LED_CTRL_GPP        MV_GPP16
#define LACIE_MAIN_POWER_CTRL_GPP       MV_GPP24
#define LACIE_HD0_LED_CTRL_GPP          MV_GPP17
#define LACIE_HD1_LED_CTRL_GPP          MV_GPP13
#define LACIE_HD0_RED_LED_CTRL_GPP      MV_GPP11
#define LACIE_HD1_RED_LED_CTRL_GPP      MV_GPP10
#define LACIE_SEL_RAID_MODE_GPP         (MV_GPP0 | MV_GPP2)

#define LACIE_HDD_ACTIVITY_CTRL_GPP     (LACIE_HD0_ACTIVITY_CTRL_GPP | LACIE_HD1_ACTIVITY_CTRL_GPP)
#define LACIE_HDD_LED_CTRL_GPP          (LACIE_HD0_LED_CTRL_GPP | LACIE_HD1_LED_CTRL_GPP)
#define LACIE_HDD_RED_LED_CTRL_GPP      (LACIE_HD0_RED_LED_CTRL_GPP | LACIE_HD1_RED_LED_CTRL_GPP)

/* --- GPP mapped to interrupt mask --- */
/* N.B.: Select MPP pins that are supposed to operate as interrupt lines */

#define LACIE_POWER_SWITCH_ON_IRQ   IRQ_GPP_8
#define LACIE_POWER_SWITCH_OFF_IRQ  IRQ_GPP_9
#define LACIE_PUSH_BUTTON_IRQ       IRQ_GPP_18

#define DB_CUSTOMER_BOARD_GPP_INTS_MASK ( LACIE_POWER_SWITCH_ON_GPP     \
                                        | LACIE_POWER_SWITCH_OFF_GPP    \
                                        | LACIE_PUSH_BUTTON_GPP         \
                                        )

/* --- GPP Info for devices linked to GPIO --- */

#define DB_CUSTOMER_BOARD_GPP_INFO_LIST_CNT  0x2
#define DB_CUSTOMER_BOARD_GPP_INFO_LIST      {BOARD_DEV_USB_VBUS, 22} /* USB-CTL 1 on GPP22 */ \
                                            ,{BOARD_DEV_USB_VBUS, 1}  /* USB-CTL 2 on GPP1  */

#else
#error "#### THIS BOARD DEFINITION SHOULD NOT HAVE BEEN LOADED - Please fix me ####"
#endif /* defined(CONFIG_LACIE_2BIG) */
5Big:
Code: Select all
#if defined(CONFIG_LACIE_5BIG)

/* --- Board ID --- */
/* This is displayed by both Uboot and Linux during the boot process                                 */
/* N.B.: The name reported from U-Boot must match the exact name stored in the board's configuration */

#define DB_CUSTOMER_BOARD_NAME  "DB-88F5281-LaCie"

/* --- I2C Devices --- */
#define DB_CUSTOMER_BOARD_I2D_DEV_LIST_CNT  2
#define DB_CUSTOMER_BOARD_I2D_DEV_LIST      { 0x32, 0x50 }

/* --- Device CS --- */
/* {CS type, params, devType, devWidth}*/

#define DB_CUSTOMER_BOARD_DEVCS_LIST_CNT    1
#define DB_CUSTOMER_BOARD_DEVCS_LIST        {3, 0x8fcfffff, BOARD_DEV_NOR_FLASH, 8} /* bootCs */                   

/* --- MPP/GPP mapping --- */
/* ---
   --- Set MPPSel registers in order to map the MPP in the following way
   ---

   MPP#    |      Description     |         ID          | Purpose (values from MSB to LSP)
   ---------------------------------------------------------------------------------------------------------------
      0    |     GPP - Output     | SHUTDOWN_REG        |req cpu power off
      1    |     GPP - Input      | USB-CTL1            | Power ctrl on USB port 1: OK(1) or FAIL(0)
      2    |     GPP - Input      | REQ_PWR_HDD0        |req power on/off hdd's(1 active)
      3    |     GPP - Input      | BOARD_IDENT (0)     | HW Board ID bit 0 (cf. MPP#12)
      4    |     GPP - Input      | PB                  | front eye button (1 active)
      5    |     GPP - Output     | CDE_LED             | cmd front blue led '0' led off (slow
           |                      |                     | blink by cpu) '1' led on
      6    |     GPP - Output     | LED_FAIL            | Front LED Red : 1 active
      7    |     GPP - Output     | PWRON_BLINKING      | Control initial Red/Blue HW blinking STOP(1), CONTINUE(0)
     8-9   |   GPP - Input/INTR   | SW_ON & SW_OFF      | Power switch : ON(01b), AUTO(00b) or OFF(10b)
      10   |     GPP - Output     | FAIL_HD1            | Red LED for HD1 : ON(1), OFF(0)
      11   |     GPP - Output     | FAIL_HD0            | Red LED for HD0 : ON(1), OFF(0)
      12   |     GPP - Input      | BOARD_IDENT (1)     | HW Board ID bit 1 (00b)
      13   |     GPP - Output     | FAIL_HD2            | Red LED for HD2 : ON(1), OFF(0)
      14   |     GPP - Output     | FAIL_HD3            | Red LED for HD3 : ON(1), OFF(0)
      15   |     GPP - Output     | FAIL_HD4            | Red LED for HD4 : ON(1), OFF(0)
      16   |     GPP - Output     | FAN_TEST            | Force ctn trip point active
      17   |     GPP - Input      | FAN_ON              | Fan driving detection
      18   |   GPP - Input        | FAN-FAI             | Fan rotation failing detection
    20      |    PCI-INT0          | PCI interrupT       | N/A
   -----------------------------------------------------------------------
   ---
*/
#define DB_CUSTOMER_BOARD_MPP0_7    0x00000003  /*|                   */
#define DB_CUSTOMER_BOARD_MPP8_15   0x00000000  /*|-> MPP/GPP mapping */
#define DB_CUSTOMER_BOARD_MPP16_23  0x00000000  /*|                   */
#define DB_CUSTOMER_BOARD_MPP_DEV   0x00160000
#define DB_CUSTOMER_BOARD_GPP_OE    0xfffe131a  /* Bit mask for GPP direction (1-In, 0-Out) */

#define DB_CUSTOMER_BOARD_GPP_VAL   0xe4        /* Bit mask for the value Output GPP        */

#define DB_CUSTOMER_BOARD_GPP_POL   N_A

/* --- GPP IN devices map --- */

#define LACIE_HW_BOARD_ID_GPP       (MV_GPP3 | MV_GPP12)
#define LACIE_FAN_ACTIVITY_GPP      MV_GPP17
#define LACIE_FAN_STATUS_GPP        MV_GPP16
#define LACIE_POWER_SWITCH_ON_GPP   MV_GPP8
#define LACIE_POWER_SWITCH_OFF_GPP  MV_GPP9
#define LACIE_POWER_SWITCH_GPP      (LACIE_POWER_SWITCH_ON_GPP | LACIE_POWER_SWITCH_OFF_GPP)
#define LACIE_PUSH_BUTTON_GPP       MV_GPP4
#define LACIE_USB_POWER_STATUS_GPP  MV_GPP1

/* --- GPP OUT devices map --- */

#define LACIE_HDD_POWER_CTRL_GPP        MV_GPP2
#if 0
#define LACIE_HDD_POWER_STATUS_GPP      (MV_GPP23 | MV_GPP25)
#endif

/* only for conformity .... the gpps for hdd are failure signal*/
#define LACIE_FRONT_RED_LED_CTRL_GPP    MV_GPP6
#if 0                   
/* for hdd led, we control only the red, activity control is too complicated
 * and must be implemented throught sata controller
 */
#define LACIE_HD0_ACTIVITY_CTRL_GPP     MV_GPP11
#define LACIE_HD1_ACTIVITY_CTRL_GPP     MV_GPP10
#define LACIE_HD2_ACTIVITY_CTRL_GPP     MV_GPP13
#define LACIE_HD3_ACTIVITY_CTRL_GPP     MV_GPP14
#define LACIE_HD4_ACTIVITY_CTRL_GPP     MV_GPP15
#endif

#define LACIE_FRONT_LED_BLINK_CTRL_GPP  MV_GPP7
#define LACIE_FRONT_LED_CTRL_GPP        MV_GPP5

#define LACIE_MAIN_POWER_CTRL_GPP       MV_GPP0

#define LACIE_HD0_RED_LED_CTRL_GPP      MV_GPP11
#define LACIE_HD1_RED_LED_CTRL_GPP      MV_GPP10
#define LACIE_HD2_RED_LED_CTRL_GPP      MV_GPP13
#define LACIE_HD3_RED_LED_CTRL_GPP      MV_GPP14
#define LACIE_HD4_RED_LED_CTRL_GPP      MV_GPP15

/* --- GPP mapped to interrupt mask --- */
/* N.B.: Select MPP pins that are supposed to operate as interrupt lines */

#define LACIE_POWER_SWITCH_ON_IRQ   IRQ_GPP_8
#define LACIE_POWER_SWITCH_OFF_IRQ  IRQ_GPP_9
#define LACIE_PUSH_BUTTON_IRQ       IRQ_GPP_4

#define DB_CUSTOMER_BOARD_GPP_INTS_MASK ( LACIE_POWER_SWITCH_ON_GPP     \
                                        | LACIE_POWER_SWITCH_OFF_GPP    \
                                        | LACIE_PUSH_BUTTON_GPP         \
                                        )

/* --- GPP Info for devices linked to GPIO --- */
#if 0
/* was necessary to include this on the c-side ...
 */

/* PCI_IF */
#define DB_CUSTOMER_BOARD_PCI_IF_NUM 1
#define DB_CUSTOMER_BOARD_PCI_IF dbCustomerBoardPciIf

static MV_BOARD_PCI_IF dbCustomerBoardPciIf[DB_CUSTOMER_BOARD_PCI_IF_NUM] =
/* {pciDevNum, {intAGppPin, intBGppPin, intCGppPin, intDGppPin}}*/
   {
   {7, {N_A, N_A, N_A, N_A}}               /* pciSlot0*/
   };

/* MAC config: specify MAC speed and Phy address per ethernet interface*/
#define DB_CUSTOMER_BOARD_MAC_INFO_NUM 1
#define DB_CUSTOMER_BOARD_MAC_INFO dbCustomerBoardMacInfo

static MV_BOARD_MAC_INFO dbCustomerBoardMacInfo[DB_CUSTOMER_BOARD_MAC_INFO_NUM] =
/* {{MV_BOARD_MAC_SPEED boardmacSpeed, MV_U8 boardEthSmiAddr}} */
   {
      {BOARD_MAC_SPEED_AUTO, 0x8} /* egiga0*/
   };


#endif
#else
#error "#### THIS BOARD DEFINITION SHOULD NOT HAVE BEEN LOADED - Please fix me ####"
#endif /* defined(CONFIG_LACIE_5BIG) */
The most scaring part is that the 5big seems to have pci. But I don't know what could be connected. An extra sata chip? Anyway, the code is 'marked away' with the message: "was necessary to include this on the c-side ...". So far I didn't find anything in .c files, though.

I think if you just include sata multipliers in the 2big kernel, if might work. Fortunately taetae has serial access, so it will give a lot of information.
Mijzelf
 
Posts: 255
Joined: Wed Nov 21, 2012 9:12 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Mon Aug 26, 2013 9:50 pm

mmm...the gpio pin definition will need to be adapted as well if we want power on all disk..this will not be a quick fix.
Tomorow evening I will have some time to have a more detailed look.

ps there is a good chance that the fvdw-sl firmware might run also when using the stock kernel from lacie, only some features like nfs server and other kernel related stuff will not work.
Unfortunate the fvdw-sl console with the standalone kernel cannot be used yet for preparing a hard disk, the because the standalone kernel in the fvdw-sl console only supports the kirkwood devices on this moment. I did not made an orion standalone kernel yet.
But you could download the first time install package for the nwsp2 and prepare a hard disk following the manual guide. Instead of writing the fvdw-sl kernel to sda6 you can should write the stock kernel to sda6. Put the disk in the 5big_v1 and d see if it boots(to be honest I do not see a reason why it won't come up only some features will not work). Also you will see only one disk because the nas database we use in the nwsp2 firmware is for a single disk nas, but that can be adapted easily by adapting the database.
Later you can write the dedicated kernel to sda6 to get all features working of the fvdw-sl firmware.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: lacie 5 big network v.1 please support for fvdw

Postby taetae » Mon Aug 26, 2013 9:51 pm

I'm here ;-)

I'm 24 hours and then I have to leave for work

Image of motherboard


http://img838.imageshack.us/img838/605/8h7n.jpg
taetae
Donator VIP
Donator VIP
 
Posts: 438
Joined: Mon Aug 26, 2013 9:02 am

Re: lacie 5 big network v.1 please support for fvdw

Postby fvdw » Mon Aug 26, 2013 10:00 pm

ok, but I will go to bed now

seeing you post on nas central the stock kernel might give a problem as the initramfs it contains tries to do funny things.
That might be possible to solve by unpacking the initramfs, adapt it and put it back...
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Next

Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 1 guest