From: Pierre Michon <pierre@no-spam.org>
To: linux-kernel@vger.kernel.org
Subject: Re: freebox possible GPL violation
Date: Wed, 5 Oct 2005 18:06:45 +0200 [thread overview]
Message-ID: <20051005160645.GA1295@linux.ensimag.fr> (raw)
>> Why does it need to reboot when there is a new firmware ?
>To use it, exactly like when you reboot your pc to change kernels.
Yes but in this case you have just rebooted. It is like when you reboot
to change your kernel, the new kernel notice it is newer and reboot...
If it has an external firmware in the adsl chips for downloading the
linux kernel, why after you download the new linux firmware, you need to
reboot ?
I forgot to say that in case of a new firmware, you can see the upload
(and flash ?) of the new firmware with ____,----- symbol on led. See
step 6 of [1].
So why in case a new firmware you need to wait more time (about 10
second) that the case where there not new firmware ?
>> How they manage to download the firmware (need led driver, ppp, http,
>> adsl driver, atm stack, ...)
>How do you think some random network card with do netbooting works ?
>(got a led driver, ipv4 simplified "stack", dhcp & tftp capabilities)
>Just like your pc has a BIOS to search for booting devices
Adsl is far more complex than ethernet...
>> Please suggest other mailling lists.
>the one you CC at first @lists.gpl-violations.org and only this one ...
Ok, let's continue on this mailling list.
Register is needed to post, but I think it is worth to continue, to
clarify how works the freebox and some wrong assuptions.
Pierre
[1] http://forums.grenouille.com/index.php?showtopic=14659
next reply other threads:[~2005-10-05 16:06 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 16:06 Pierre Michon [this message]
2005-10-05 16:47 ` freebox possible GPL violation Emmanuel Fleury
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 23:26 Pierre Michon
2005-10-06 12:01 Pierre Michon
2005-10-06 13:06 ` Emmanuel Fleury
2005-10-06 13:40 ` Michael Poole
2005-10-06 14:48 ` Matan Peled
2005-10-05 17:57 Pierre Michon
2005-10-05 15:18 Pierre Michon
2005-10-05 15:49 ` Vincent Hanquez
2005-10-05 15:12 Pierre Michon
2005-10-05 15:08 Pierre Michon
2005-10-05 11:13 Pierre Michon
2005-10-05 11:22 ` Emmanuel Fleury
2005-10-05 11:27 ` Arjan van de Ven
2005-10-05 11:37 ` Emmanuel Fleury
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 12:02 ` Emmanuel Fleury
2005-10-05 12:07 ` Arjan van de Ven
2005-10-05 12:29 ` Emmanuel Fleury
2005-10-05 12:45 ` Michael Poole
2005-10-05 17:11 ` Alexandre Oliva
2005-10-06 0:07 ` Helge Hafting
2005-10-06 0:49 ` David Lang
2005-10-06 1:12 ` Stefan Smietanowski
2005-10-06 2:25 ` David Lang
2005-10-06 9:20 ` Helge Hafting
2005-10-06 9:51 ` Emmanuel Fleury
2005-10-06 9:53 ` Emmanuel Fleury
2005-10-06 11:39 ` Helge Hafting
2005-10-06 13:05 ` Emmanuel Fleury
2005-10-06 13:42 ` Michael Poole
2005-10-06 14:19 ` Helge Hafting
2005-10-06 20:15 ` Stefan Smietanowski
2005-10-11 2:27 ` David Schwartz
2005-10-11 10:48 ` Graham Murray
2005-10-05 12:15 ` Vincent Hanquez
2005-10-05 11:45 ` linux-os (Dick Johnson)
2005-10-05 11:59 ` Arjan van de Ven
2005-10-05 11:50 ` Emmanuel Fleury
2005-10-05 10:08 Pierre Michon
2005-10-05 10:18 ` Emmanuel Fleury
2005-10-05 8:47 Pierre Michon
2005-10-05 9:42 ` Helge Hafting
2005-10-15 9:40 ` Loic Dachary
2005-10-19 17:58 ` Pierre Michon
2005-10-20 15:29 ` Loic Dachary
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=20051005160645.GA1295@linux.ensimag.fr \
--to=pierre@no-spam.org \
--cc=20051005154923.GA14366@snarc.org \
--cc=linux-kernel@vger.kernel.org \
/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