From: Dave Taht <dave.taht@gmail.com>
To: Outback Dingo <outbackdingo@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] breakage
Date: Sat, 13 Oct 2012 09:42:37 -0700 [thread overview]
Message-ID: <CAA93jw6jsESEyAnoy+VRj4kyAe8OOV0BYGwv8Ydjsvf+U1yexA@mail.gmail.com> (raw)
In-Reply-To: <CAKYr3zx_vs7pteeAUU4K8ZjO2kry6sKZpwO_7onMog8p+_M8pw@mail.gmail.com>
If I did, I'd be done now. It looks mostly to be:
iproute2 moved (I had patches to that): fixed
fq_codel and ecn fixes with changed patch names: fixed
package signing: stomped on thoroughly, don't know what to do with it yet
random number generation: I'm happy the 3.5 rng stuff was backported
into 3.3.8, however that disabled IRQF_RANDOM
and it's unclear to me what level of new driver support is needed to
make the new rng stuff work better.
I care about the random number stuff a lot, (the previous situation
re real entropy and WPA was horrible) but I don't know enough about it
to tell if additional support is needed in the ath9k and ar71xx and
elsewhere to truly enable the new rng stuff. ?
I thought openwrt was freezing....
On Sat, Oct 13, 2012 at 9:36 AM, Outback Dingo <outbackdingo@gmail.com> wrote:
> On Sat, Oct 13, 2012 at 12:32 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> as is kind of usual, me submitting patches upstream to openwrt breaks
>> downstream cerowrt when they are accepted.
>>
>> I'm happy that several were accepted, too brain-dead to find and fix
>> all the conflicts induced as yet.
>
> hahahaha, do you have a list of whats been accepted?
>
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2012-10-13 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 16:32 Dave Taht
2012-10-13 16:36 ` Outback Dingo
2012-10-13 16:42 ` Dave Taht [this message]
2012-10-13 16:43 ` Dave Taht
2012-10-13 16:59 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6jsESEyAnoy+VRj4kyAe8OOV0BYGwv8Ydjsvf+U1yexA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=outbackdingo@gmail.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