mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: dan@dennedy.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	Petr Vandrovec <petr@vandrovec.name>,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix/add raw1394 CONFIG_COMPAT code
Date: Sun, 20 May 2007 17:28:18 +0200	[thread overview]
Message-ID: <46506912.9020904@s5r6.in-berlin.de> (raw)
In-Reply-To: <200705201703.37561.arnd@arndb.de>

Arnd Bergmann wrote:
> On Sunday 20 May 2007, Stefan Richter wrote:
>>> Note that this data structure only needs conversion on x86_64 and ia64, but
>>> not on powerpc and other 64 bit architectures that align __u64 also in
>>> 32 bit mode.
>> Is this conversion just unnecessary or actually harmful on ppc64 and others?
> 
> With the current patch, the compat_ioctl function does not handle the ppc32
> version of the structure at all, so it's broken there, it would at least
> need a 
> 
> 	case RAW1394_IOC_GET_CYCLE_TIMER:
> 		err = raw1394_ioctl(NULL, file, cmd, arg);
> 		break;

Dan,

maybe we should change

/* argument to RAW1394_IOC_GET_CYCLE_TIMER ioctl */
struct raw1394_cycle_timer {
	/* contents of Isochronous Cycle Timer register,
	   as in OHCI 1.1 clause 5.13 (also with non-OHCI hosts) */
	__u32 cycle_timer;

	/* local time in microseconds since Epoch,
	   simultaneously read with cycle timer */
	__u64 local_time;
};

to

/* argument to RAW1394_IOC_GET_CYCLE_TIMER ioctl */
struct raw1394_cycle_timer {
	/*
	 * least significant 32 bits are contents of Isochronous Cycle
	 * Timer register, as in OHCI 1.1 clause 5.13 (also with
	 * non-OHCI hosts)
	 */
	__u64 cycle_timer;

	/*
	 * local time in microseconds since Epoch,
	 * simultaneously read with cycle timer
	 */
	__u64 local_time;
};

before a libraw1394 with get-cycle-timer support is released.
Shall I prepare according patches for raw1394 and libraw1394?
-- 
Stefan Richter
-=====-=-=== -=-= =-=--
http://arcgraph.de/sr/

  reply	other threads:[~2007-05-20 15:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07  2:14 Petr Vandrovec
2007-05-07 16:40 ` Stefan Richter
2007-05-15  3:52 ` Dan Dennedy
2007-05-15 22:59 ` Stefan Richter
2007-05-15 23:00   ` [PATCH 1/3] ieee1394: raw1394: Fix read() for 32bit userland on 64bit kernel Stefan Richter
2007-05-15 23:01     ` [PATCH 2/3] ieee1394: raw1394: Fix write() " Stefan Richter
2007-05-15 23:02       ` [PATCH 3/3] ieee1394: raw1394: Add ioctl() " Stefan Richter
2007-05-15 23:51   ` [PATCH] Fix/add raw1394 CONFIG_COMPAT code Petr Vandrovec
2007-05-19 23:55 ` Arnd Bergmann
2007-05-20  0:02   ` Stefan Richter
2007-05-20 15:03     ` Arnd Bergmann
2007-05-20 15:28       ` Stefan Richter [this message]
2007-05-20 15:37         ` Arnd Bergmann
2007-05-20 15:55           ` Stefan Richter
2007-05-21  7:28         ` Stefan Richter
2007-05-21 16:52           ` [PATCH] ieee1394: raw1394: Add ioctl() for 32bit userland on 64bit kernel, amendment Stefan Richter
2007-05-23  4:54         ` [PATCH] Fix/add raw1394 CONFIG_COMPAT code Dan Dennedy
2007-05-23  6:32           ` Stefan Richter

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=46506912.9020904@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=arnd@arndb.de \
    --cc=dan@dennedy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=petr@vandrovec.name \
    /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

all inboxes | Powered by JetHome®