9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] pcc limitation?
Date: Sun,  7 Nov 2010 13:26:41 -0500	[thread overview]
Message-ID: <1ab89ced7625309d8c289292c4a4086c@brasstown.quanstro.net> (raw)
In-Reply-To: <4CD6D235.3030704@gmx.net>

> The big problem with defining it as an array inside struct spicmd is
> that writearr has variable length. writearr is a command sent to a SPI
> chip by a SPI controller. writearr can have any length of 1-1056 bytes.
> There's also an analogous readarr in struct spi_command (not mentioned
> in the example to keep it brief) and that one can have any length
> between 0 and 16777217 (2^24+1) bytes. One variable-length array at the
> end of a struct is possible, but an array of structs with a variable
> length array in the struct won't work since you can't compute the offset
> of individual members of the outer arrray.

what is the largest sequence of commands in practice?

- erik



  reply	other threads:[~2010-11-07 18:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07  0:56 Carl-Daniel Hailfinger
2010-11-07  4:02 ` Federico G. Benavento
2010-11-07 12:32   ` Carl-Daniel Hailfinger
2010-11-07 14:46     ` erik quanstrom
2010-11-07 16:22       ` Carl-Daniel Hailfinger
2010-11-07 18:26         ` erik quanstrom [this message]
2010-11-07 19:36           ` Carl-Daniel Hailfinger
2010-11-07 19:42             ` erik quanstrom
2010-11-08  0:16               ` Carl-Daniel Hailfinger
2010-11-08  0:56                 ` erik quanstrom
2010-11-08  9:39                   ` Julius Schmidt
2010-11-08 14:00                     ` erik quanstrom
2010-11-08 15:17                       ` Anthony Sorace
2010-11-08  2:58         ` Russ Cox

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=1ab89ced7625309d8c289292c4a4086c@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).