Brian J. Murrell wrote:
> On Thu, 2009-01-08 at 20:33 -0500, Jose Vasconcellos wrote:
>
>> Attached is a patch to handle the mounting and unmounting
>> of blocked device. This handles both USB and IEEE1394
>> devices. It removes /sbin/usb-storage in favor of using the
>> block hotplug event.
>>
Markus Wigge wrote:
>> Make it x86 specific and I'll commit it. No sense in building modules on
>> platforms that will never use them.
> done.
Committed in r13920, tweaked to build on olpc in r13933
Also worth noting that someone pointed out the Lemote Fuloong netbook
uses the CS5536 with a Long
On Thu, 2009-01-08 at 20:33 -0500, Jose Vasconcellos wrote:
> Attached is a patch to handle the mounting and unmounting
> of blocked device. This handles both USB and IEEE1394
> devices. It removes /sbin/usb-storage in favor of using the
> block hotplug event.
Sweet. Any chance you tested this fo
Jose Vasconcellos wrote:
Attached is a patch to handle the mounting and unmounting
of blocked device. This handles both USB and IEEE1394
devices. It removes /sbin/usb-storage in favor of using the
block hotplug event.
Signed-off-by: Jose Vasconcellos
Seems very hard to get the patch right on t
Attached is a patch to handle the mounting and unmounting
of blocked device. This handles both USB and IEEE1394
devices. It removes /sbin/usb-storage in favor of using the
block hotplug event.
Signed-off-by: Jose Vasconcellos
Index: package/base-files/files/etc/hotplug.d/ieee1394/10-ieee1394
===
So we get back to a fundamental point of what is the role of
contributors (those without SVN access) in OpenWrt. But this
is not about SVN access but to understand the goals of the
project and how to let the community participate.
Stanislav Sinyagin wrote:
> I didn't yet touch T2 deeper than addin
OpenEmbedded has overlay functionality to allow you to do that.
But further discussion of that should be on an OE mailing list, not an OpenWrt
one.
-- Rod
-Original Message-
From: Stanislav Sinyagin
Date: Friday, Jan 9, 2009 7:44 am
Subject: Re: [OpenWrt-Devel] OpenWrt development proces
I didn't yet touch T2 deeper than adding it to my bookmarks, but what I
dislike in OpenWRT is that if you need to build a new target, you have
to patch a ton of Makefiles, with the risk that your patches will never
be accepted.
What would be really cool, is a system that lets you customize eve
The OpenWrt build system is designed by someone who loves Makefiles.
The OpenEmbedded build system is designed by someone who despises Makefiles.
T2 seems to be run by someone who despises other open source projects (read the
website to make your own judgement).
You'll never be able to merge any
On Thu, Jan 8, 2009 at 11:05, Chiang Kang Tan wrote:
> Hi all,
>
> I'm having problem trying to use ip utility in iproute2 to set up some
> routing rules. Basically as soon as I try to use ip rule, e.g.
>
> # ip rule add
>
> I get the following error:
>
> RTNETLINK answers: Address family not sup
Hi all,
I'm having problem trying to use ip utility in iproute2 to set up some routing
rules. Basically as soon as I try to use ip rule, e.g.
# ip rule add
I get the following error:
RTNETLINK answers: Address family not supported by protocol.
And "ip rule show" returns me nothing, when I ex
I like my WL-700gE and recently went through the trouble to take an
older package for its RTC driver and update it.
I'm not sure if the package is in a good enough shape for inclusion, but
I'd like to know what needs to be done now in order to get it included.
There's a trac ticket for it at http
Speaking of distributions, T2 is also worth looking at:
http://www.t2-project.org/
I was going to spend some time in learning it deeper, but the Christmas holidays
appeared to be too short :)
- Original Message
> From: Jose Vasconcellos
> I think this topic merits additional discussio
Gregers Petersen wrote:
> Stefan Monnier wrote:
>
>>> OpenWrt is described as a Linux distribution for embedded devices.
>>>
>>> (ok. It was a kind of joke, but this is actually the goal of OpenWrt; to
>>> develop a Linux based embedded system for both final solutions and
>>> developm
14 matches
Mail list logo