list the module on their
> > machines? Could the kernel driver be fixed upstream to not be active on
> > devices that will be broken?
>
> Unfortunately I cannot remember (and I cannot even read the commit
> messages right now because Alioth is done). IIRC I disabled it based
>
On Fri, Apr 27, 2007 at 08:26:10AM -0500, Eric Sandeen wrote:
> >Yep. Padding rules on old-ABI ARM systems are 'special', but still
> >spec-compliant. See:
>
> Thanks, I've read up a bit since, and I think I grok it now :)
>
> So, adding __attribute__((packed)) to xfs_dir2_sf_off_t,
> xfs_dir
On Thu, Apr 26, 2007 at 11:34:56PM -0500, Eric Sandeen wrote:
> Root cause seems to be gcc misaligning the xfs shortform directory
> structures. In the example below, bar.parent has offset 4, while
> boo.parent has offset 2. The union seems to cause extra padding - I
> believe "c" should be a
On Thu, Apr 26, 2007 at 11:57:40PM -0500, Eric Sandeen wrote:
> Maybe the alignment isn't broken; it's just "special" - I guess there
> are no actual rules on how the structure must be aligned... hmm...
Yep. Padding rules on old-ABI ARM systems are 'special', but still
spec-compliant. See:
Attached is a new patch that:
* Drops both footbridge and rpc from the armel flavour list.
(Martin Michlmayr.)
* Adds CONFIG_AEABI=y/CONFIG_OABI_COMPAT=y to config.iop32x and
config.ixp4xx as well, since they seem to override the main
config. (Joey Hess)
Apply as follows:
cp -a deb
5 matches
Mail list logo