Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Kreileder <jk@blackdown.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd-ioctl32 is failing on x86_64 (no crashes, just errors)
Date: Fri, 14 Jan 2005 07:13:39 +0100	[thread overview]
Message-ID: <87wtuga67g.fsf@blackdown.de> (raw)
In-Reply-To: <20050112022402.GB9290@lion.gg3.net> (Georgi Georgiev's message of "Wed, 12 Jan 2005 11:24:02 +0900")

Georgi Georgiev <chutz@gg3.net> writes:

>> Index: alsa-kernel/core/ioctl32/ioctl32.c
>> ===================================================================
>> RCS file: /home/tiwai/cvs/alsa/alsa-kernel/core/ioctl32/ioctl32.c,v
>> retrieving revision 1.30
>> diff -u -r1.30 ioctl32.c
>> --- alsa-kernel/core/ioctl32/ioctl32.c	15 Dec 2004 15:26:24 -0000	1.30
>> +++ alsa-kernel/core/ioctl32/ioctl32.c	10 Jan 2005 16:59:33 -0000
>> @@ -219,25 +219,10 @@
>> 	struct sndrv_ctl_elem_id id;
>> 	unsigned int indirect;	/* bit-field causes misalignment */
>> union {
>> -		union {
>> -			s32 value[128];
>> -			u32 value_ptr;
>> -		} integer;
>> -		union {
>> -			s64 value[64];
>> -			u32 value_ptr;
>> -		} integer64;
>> -		union {
>> -			u32 item[128];
>> -			u32 item_ptr;
>> -		} enumerated;
>> -		union {
>> -			unsigned char data[512];
>> -			u32 data_ptr;
>> -		} bytes;
>> -		struct sndrv_aes_iec958 iec958;
>> +		s32 integer[128];	/* integer and boolean need conversion */
>> +		unsigned char data[512];	/* others should be compatible */
>> } value;
>> -        unsigned char reserved[128];
>> +        unsigned char reserved[128];	/* not used */
>> };

That breaks alignment on ppc64 again.  Fix:

--- ioctl32.c.orig	2005-01-14 06:53:41.496899917 +0100
+++ ioctl32.c	2005-01-14 06:56:26.146675819 +0100
@@ -220,6 +220,7 @@ struct sndrv_ctl_elem_value32 {
 	unsigned int indirect;	/* bit-field causes misalignment */
         union {
 		s32 integer[128];	/* integer and boolean need conversion */
+		s64 longint[64];
 		unsigned char data[512];	/* others should be compatible */
         } value;
         unsigned char reserved[128];	/* not used */
=


        Juergen

-- 
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux/java2-status/


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  parent reply	other threads:[~2005-01-14  6:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 13:06 snd-ioctl32 is failing on x86_64 (no crashes, just errors) Georgi Georgiev
2005-01-07 10:45 ` Takashi Iwai
2005-01-08  7:40   ` Georgi Georgiev
2005-01-10 11:26     ` Takashi Iwai
2005-01-10 12:33       ` Georgi Georgiev
2005-01-10 13:39         ` Takashi Iwai
2005-01-10 16:15           ` Georgi Georgiev
2005-01-11 13:11             ` Takashi Iwai
2005-01-12  2:24               ` Georgi Georgiev
2005-01-12 11:20                 ` Takashi Iwai
2005-01-14  6:13                 ` Juergen Kreileder [this message]
2005-01-14 10:26                   ` Takashi Iwai
2005-01-14 10:59                     ` Juergen Kreileder
2005-01-14 11:01                       ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wtuga67g.fsf@blackdown.de \
    --to=jk@blackdown.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox