<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Gergely,<br>
<br>
I'm just curious to know what makes you be "pretty sure" that many
vendors will start doing this in the future and overcome the
possible legal or political issues they may have to do that ? Marvel
was one of the worst cases I've ever seen here and I have no much
idea what made them to release it (a miracle maybe?). Unless you
were referring to "in the future" as next century I don't see that
happening that soon.<br>
<br>
Other than that I fully agree OpenWrt is great, well developed and
maintained.<br>
<br>
Best,<br>
<br>
<div class="moz-cite-prefix">On 10/03/2015 17:26, Gergely Kiss
wrote:<br>
</div>
<blockquote
cite="mid:CAF-mK=UmOhOYOax_MSL-KEJcLkXAH-q4dZfU=ixdQzAPDP97qw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>Hi Valent,<br>
<br>
</div>
first of all, I strongly disagree with people claiming
that OpenWrt sucks because it doesn't. For me it
rather looks like a well-maintained, rapidly improving
project with a great number of actively supported
hardware and quite a few people contributing to the
project regularly. I can see dozens of patches
published every day not only by the core devs but by
many contributors which is a great thing and indicates
that many people are trying to make OpenWrt <b>even </b>better.<br>
<br>
I must mention you had a point that made me smile -
it's about being a miracle that openwrt works as good
as it does. This reminded me to the DNS system. As we
all know, it was never developed with a concept of
creating a complex network service to be used in a
worldwide network but more like as a simple
"phonebook" for companies, schools and other small,
autonomous institutions to avoid the need to remember
IP addresses. Now, DNS is used worldwide by thousands
of entities and is probably one of the oldest
protocols still actively used on the internet and it
still works pretty good despite its age. Miracles do
happen sometimes and that's what makes our lives
brighter. :)<br>
<br>
</div>
</div>
Anyway, as far as I can see, more and more manufacturers
(including wireless chip vendors) realize the benefits of
open source and release their driver codes to the open
source community. I clearly remember seeing some driver
sources posted on this list directly by Marvell and I'm
pretty sure that many other vendors will start doing so in
the future. I think the reason why most vendors still
haven't published their drivers is more like legal issues
rather than technical or "political" ones. They have to
meet regulatory requirements and respect the copyright of
other people's work. Even if they would feel inclined to
release their driver, they can't do so because of
licensing issues.<br>
<br>
</div>
For people complaining about OpenWrt, I would simply tell
them that first of all, it's provided for free for everyone
in the world so stop complaining. Also, being an open source
project, it's always open for contributions. Everyone has
the possibility to share ideas or implement features making
OpenWrt a more stable, more robust and more versatile piece
of software.<br>
<br>
</div>
<div>My fifty cents was to create a port of Seafile for
OpenWrt - I'm using it myself at home and I'm very happy to
see it running on my router with a USB HDD attached rather
than running an additional home server 24/7 consuming more
power and taking up more room in my flat. At the same time,
I'm happy to provide the same ability to other people
because that's how it's meant to be.<br>
<br>
Do you think OpenWrt sucks? Then stop complaining and do
something to make it better. It's that simple.<br>
</div>
<div><br>
</div>
Cheers,<br>
</div>
Gergely<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 9 March 2015 at 21:02, <a
moz-do-not-send="true"
href="mailto:valent.turkovic@gmail.com">valent.turkovic@gmail.com</a>
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:valent.turkovic@gmail.com" target="_blank">valent.turkovic@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
I see this or similar question of forums all the time and I
have<br>
answered it few times. I suggest we open a wiki page and
contribute an<br>
answer.<br>
<br>
Here is how I usually reply to similar questions, please
give your<br>
comments in your replies:<br>
<br>
<br>
Why it OpenWrt slower than stock firmware? I can help by
shining a bit<br>
of light onto this subject. I'm developing custom firwmares
based on<br>
OpenWrt but I'm not OpenWrt developer, still as I have few
years of<br>
experience with OpenWrt I can explain why sometimes
performance sucks<br>
or there are some issues and bugs.<br>
<br>
OpenWrt has three main parts; linux kernel, software
packages and<br>
wireless drivers. OpenWrt developers work on all of them.
Consider the<br>
amount of code this is, and consider that all work is done
by a<br>
handful of OpenWrt developers. If you work in software
industry you<br>
know many people big companies hire to work on much smaller
projects.<br>
So be thankful it works as good as it does, it is actually a
miracle<br>
that it works as good as it does<br>
<br>
Main issue is that wifi chip manufacturers don't offer open
source<br>
wifi drivers. If Atheros and Broadcom understood Open source
as Intel<br>
does then you would get absolutely top speed and reliability
from<br>
OpenWrt wifi drivers. You don't get top notch performance
with OpenWrt<br>
because Atheros and Broadcom are choosing not release
quality open<br>
source drivers.<br>
<br>
Linux, BSDx and OpenWrt developers can only use other means
to get<br>
wifi devices to work, usually reverse engineering, and
without support<br>
from wifi chip companies it is not easy to support all
features, get<br>
awesome performance and stability.<br>
<br>
This is a long way of saying, that if performance sucks on
OpenWrt you<br>
should blame Atheros and Broadcom for not giving you
(OpenWrt<br>
community) high quality open source drivers!<br>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a><br>
<a moz-do-not-send="true"
href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel"
target="_blank">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
openwrt-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel">https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>