From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: uweigand@de.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc/rfa] [1/4] SPU enhancements: preparation
Date: Fri, 15 Jun 2007 15:50:00 -0000 [thread overview]
Message-ID: <200706151549.l5FFnwYp021247@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200706021931.l52JVBZQ005084@d12av02.megacenter.de.ibm.com> (uweigand@de.ibm.com)
> Date: Sat, 2 Jun 2007 21:31:11 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
>
> Hello,
>
> this is a small fix in preparation for adding extended SPU query support.
> Some files in spufs accessed via the spu_proc_xfer_spu routines in
> spu-linux-nat.c and gdbserver/spu-low.c are non-seekable. Currently,
> any attempt to access those at non-zero offset results in a failure.
Are these files inherently non-seekable (side-effects?) or is this
just a Linux quirk you're trying to work around?
next prev parent reply other threads:[~2007-06-15 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 19:31 Ulrich Weigand
2007-06-04 19:27 ` Daniel Jacobowitz
2007-06-12 14:40 ` Ulrich Weigand
2007-06-15 15:50 ` Mark Kettenis [this message]
2007-06-15 15:54 ` Ulrich Weigand
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=200706151549.l5FFnwYp021247@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/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