From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] these are release of 9front?
Date: Sat, 12 Jan 2013 14:47:03 +0000 [thread overview]
Message-ID: <203b05c4009a4db4ea303ac8ab1a03d5@hamnavoe.com> (raw)
In-Reply-To: <681ab57d949099572c6f4f37c3844040@hamnavoe.com>
> Actually the pi is a special case
... and I was just quoting size figures for that because I had them handy.
The question of embedding things in usbd applies to other architectures too.
I find the embedding problematic, not because of memory size, but because
it gets in the way when trying to develop and test different versions of
drivers. That's why I added the 'noauto' command to /dev/usbdctl (must
document it soon).
Also the decision of what to auto-start can depend on the machine
configuration, and it feels wrong to have that information compiled in
to the kernel or even into the usbd command. It seems to me that it
should be in some sort of script or config file that can be varied
per machine or class of machine.
next prev parent reply other threads:[~2013-01-12 14:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 1:07 Francesco Cardi
2013-01-08 1:17 ` John Floren
2013-01-08 1:27 ` sl
2013-01-08 9:09 ` Richard Miller
2013-01-08 9:59 ` cinap_lenrek
2013-01-08 10:15 ` Richard Miller
2013-01-08 10:36 ` cinap_lenrek
2013-01-08 10:52 ` Richard Miller
2013-01-08 11:10 ` lucio
2013-01-08 11:24 ` Bence Fábián
2013-01-08 14:14 ` steve
2013-01-08 15:37 ` erik quanstrom
2013-01-08 13:48 ` sl
2013-01-08 16:22 ` Wes Kussmaul
2013-01-08 14:24 ` cinap_lenrek
2013-01-08 14:33 ` cinap_lenrek
2013-01-08 14:52 ` David Leimbach
2013-01-08 15:53 ` Nemo
2013-01-08 19:38 ` Richard Miller
2013-01-08 20:40 ` mveety
2013-01-08 20:48 ` erik quanstrom
2013-01-08 20:54 ` Matthew Veety
2013-01-08 22:42 ` Federico G. Benavento
2013-01-09 4:23 ` cinap_lenrek
2013-01-12 13:48 ` Richard Miller
2013-01-12 14:12 ` erik quanstrom
2013-01-12 14:35 ` Richard Miller
2013-01-12 14:47 ` Richard Miller [this message]
2013-01-08 19:18 ` erik quanstrom
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=203b05c4009a4db4ea303ac8ab1a03d5@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).