| To: | Geert Uytterhoeven <geert@linux-m68k.org> |
|---|---|
| Subject: | Re: [MIPS] Resolve compile issues with msp71xx configuration |
| From: | Shane McDonald <mcdonald.shane@gmail.com> |
| Date: | Tue, 28 Apr 2009 00:21:09 -0600 |
| Cc: | Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9aWA6ERNdm7KKDDVA/kxQK+n9Mi+a63m1eMgmzu8mCk=; b=hdPQnzKHdo/ox+Ua4dDbeMEaR1jTbXPwVF8y0T3W1ytiXtDcj6iRWZ6kI6N4IEW63k Ue7m8MUbj3Q2kJlVBfpNjGeOF4CGJJlE3Oq2TNkfSe+gbkNs7X8MHmqnX6y6U/yCWeIG nlZ5lL3z1MTv1fmdDhkwVVVT78UlbQ+yyviwI= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XoaTVSXSBvc/zfgABy6IMgwkTcAFqxWhc8W7P6PkXvrkz2s5cdOOrztr+GaUMx+gel pbSxqr9P3ioOXjA795RLYOj+5a7J89hSMVICr4/EzmmkzB396xURXZEa07jaH6vWmtSc 8J3zEh/xAWN8WkVG/ccy3u1UkobWmJkPqu9DU= |
| In-reply-to: | <10f740e80904270622u730ba067g660257847dc526de@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <E1LyQQX-00047N-6E@localhost> <20090427130952.GA30817@linux-mips.org> <10f740e80904270622u730ba067g660257847dc526de@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
|
Hello: On Mon, Apr 27, 2009 at 7:22 AM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
I am not sure how to proceed here. My main purpose in providing this patch was to get the msp71xx platform compiling again, but I stumbled into some pre-existing code ugliness, which I must confess I was ultimately responsible for. As Geert said, I need to reach deep into the squashfs internals to access the bytes_used field of struct squashfs_super_block; the code just previous to this line works similar for the cramfs filesystem, where it accesses the size field of the struct cramfs_super field. The cramfs code doesn't look as bad, because its superblock structure is defined in an easier-to-access file (linux/cramfs_fs.h). I can see a number of possible paths here: 1. Fix up the existing patch with le{32,64}_to_cpu() as Geert suggested, and leave everything else as-is. 2. Approach the squashfs maintainers to move the squashfs_fs.h file to a more public location, and still do 1. 3. Pull the squashfs code entirely. 4. Remove the entire get_ramroot() code, both squashfs and cramfs, as Christoph has suggested. I am hesitant to do this as it also affects code in the MTD subsystem (file maps/pmcmsp-ramroot.c), and it also loses some functionality on the PMC boards (putting the rootfs in RAM immediately following the kernel). Perhaps there's a better way to handle this? I am open to suggestions on how to proceed.
Shane |
| Previous by Date: | [MIPS] Resolve use of non-existent GPIO routines in msp71xx reset, Shane McDonald |
|---|---|
| Next by Date: | Re: [MIPS] Resolve compile issues with msp71xx configuration, Geert Uytterhoeven |
| Previous by Thread: | Re: [MIPS] Resolve compile issues with msp71xx configuration, Geert Uytterhoeven |
| Next by Thread: | Re: [MIPS] Resolve compile issues with msp71xx configuration, Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |