On 21/05/19 12:11, Petr Štetiar wrote:
Alberto Bursi [2019-05-21 11:37:31]:
The only clear thing is that documentation does not write itself and that
you can't rely on users to write developer documentation.
You actually can enforce it somehow, as you either include/update
documentation to r
Alberto Bursi [2019-05-21 11:37:31]:
> The only clear thing is that documentation does not write itself and that
> you can't rely on users to write developer documentation.
You actually can enforce it somehow, as you either include/update
documentation to reflect your changes or your contributio
On 21/05/19 11:13, Petr Štetiar wrote:
Linus Walleij [2019-05-20 23:48:41]:
[adding Alberto, Thomas and Javier to the Cc: loop]
how you want the sysupgrade to work.
it's just preferred to share as much common code as possible.
Maybe we could open a documentation page for new devices, like
Linus Walleij [2019-05-20 23:48:41]:
[adding Alberto, Thomas and Javier to the Cc: loop]
> how you want the sysupgrade to work.
it's just preferred to share as much common code as possible.
> Maybe we could open a documentation page for new devices, like here is how
> we want you to implement
On AR71xx the reset of each module uses such a sequence:
ath79_device_reset_set(module_bit);
ath79_device_reset_clear(module_bit);
Seems like the reset bits are not self-clearing and polling
for the reset to be finished is not possible.
Is there any Atheros documentation of the per-module rese
feel free to suggest where i can make observations as i peruse the
openwrt web and wiki pages, since i don't want to waste the list's
time with minor pedantry.
on the main openwrt page (https://openwrt.org/), over on the right
under "Latest release: 12.09", while the "Download" link takes you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There isn't.
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAzUfcACgkQdputYINPTPNcQwCglRhv+KtZlZWtINUrsnRdGezX
YEIAnjoyOEq5jPaXy6S6vKBDGC/YiDd0
=B0v
Might anyone know if updated and/or translated documentation for the
freifunk-watchdog service is available somewhere? All I can find is
the somewhat outdated German wiki page below:
http://wiki.freifunk.net/Kamikaze/LuCI/Watchdog
--
Ben West
http://gowasabi.net
b...@gowasabi.net
__
I have attached new versions of:
openwrt.tex
getting_started.tex
Makefile
I've been trying to pull the recent additions together - please comment :-)
--
Gregers Petersen, Anthropologist
[EMAIL PROTECTED]
www.wireless-ownership.org
[EMAIL PROTECTED]
getting_started.tex
Description: TeX docu
Gregers Petersen wrote:
> I would like to call for a Documentation-Team meeting on the following
> saturday (3th of November) from UTC 21.00, on IRC #openwrt-devel
>
> Subjects:
>
> 1. Getting a roadmap together.
> 2. Practical editing.
> 3. what else?
Since I currently don't have that much time
I would like to call for a Documentation-Team meeting on the following
saturday (3th of November) from UTC 21.00, on IRC #openwrt-devel
Subjects:
1. Getting a roadmap together.
2. Practical editing.
3. what else?
Sincerely
--
Gregers Petersen, Anthropologist
[EMAIL PROTECTED]
www.wireless-owne
Gregers Petersen wrote:
> I was just wondering about the following:
>
>
> On http://openwrt.org/ the link to 'Documentation' leads here:
> http://downloads.openwrt.org/kamikaze/docs/openwrt.html
>
> On http://downloads.openwrt.org/ the link to 'Documentation' leads here:
> http://wiki.openwrt.or
I was just wondering about the following:
On http://openwrt.org/ the link to 'Documentation' leads here:
http://downloads.openwrt.org/kamikaze/docs/openwrt.html
On http://downloads.openwrt.org/ the link to 'Documentation' leads here:
http://wiki.openwrt.org/
This could be a confusing elemen
Hi all
I'm going off to Hamburg in a few hours and will be there for a couple
of days. I'm going to meet up with a few of the dev's - so I thought
maybe we should try to logon to #openwrt-devel on saturday from UTC
18.00 and onwards through the nights/day?
Apart from WIP-Day September will take p
Andy Boyett wrote:
> At this point in time, I feel like that falls under one of my comments; "A
> lot of us use OpenWrt for other purposes, but we acknowledge these purposes
> are not the focus of the project."
>
> OpenWrt may be branching out into other directions, I was merely trying to
>
David Farning wrote:
>
> I was looking at the community wiki vs the dev wiki. I assume that
> the reason for this was for information quality control and preventing
> vandalism. Or is there something in the bug tacker that makes the
> separate wiki necessay. Some thoughts.
>
>>From a style
Felix Fietkau wrote:
> The wiki on https://dev.openwrt.org would probably be a better place for this
> kind of information. All developers have write access to it and we can add
> accounts for members of the documentation team as well.
>
I would like to second the suggestion by Felix
--
Grege
Gregers Petersen wrote:
>
> Andy Boyett wrote:
>
>>> what it the scope? In term of devices is it just routers, or network
>>> related devices, or embedded devices in general. This is not just a
>>> question of what openwrt can be used on, but rather what does the team
>>> think in can do well.
>
Andy Boyett wrote:
>> what it the scope? In term of devices is it just routers, or network
>> related devices, or embedded devices in general. This is not just a
>> question of what openwrt can be used on, but rather what does the team
>> think in can do well.
> I'm not a developer, but it has
Nathan Van Fleet wrote:
> I don't think everyone needs access. Provided a few people act as
> editors for full submissions and corrections, it should be fine.
>
I agree
> I think from here we should choose the editor(s) and then list what
> should be documented.
I feel like just writing "ec
David Farning wrote:
> On Wed, Sep 19, 2007 at 11:50:16AM +0200, Felix Fietkau wrote:
>> Andy Boyett wrote:
Do we want the wiki to be a comprehensive data base on network devices?
>>> The wiki was the primary form of documentation for White Russian; the
>>> OpenWrt community appears to lack th
On Wed, Sep 19, 2007 at 11:50:16AM +0200, Felix Fietkau wrote:
> Andy Boyett wrote:
> >> Do we want the wiki to be a comprehensive data base on network devices?
> > The wiki was the primary form of documentation for White Russian; the
> > OpenWrt community appears to lack the moderation required fo
Andy Boyett wrote:
>> Do we want the wiki to be a comprehensive data base on network devices?
> The wiki was the primary form of documentation for White Russian; the
> OpenWrt community appears to lack the moderation required for a successful
> wiki. Correcting the misinformation was often reverted
David Farning wrote:
> As a jumping off point for the documentation. I was wondering in the
> core developers would be willing to think about a mission statement
> for openwrt?
>
> I like the new paragraph on the web page as a starting point. Really,
> this is just a way to define ourselves so w
As a jumping off point for the documentation. I was wondering in the
core developers would be willing to think about a mission statement
for openwrt?
I like the new paragraph on the web page as a starting point. Really,
this is just a way to define ourselves so we can keep on focus.
Some possia
I don't think everyone needs access. Provided a few people act as
editors for full submissions and corrections, it should be fine.
I think from here we should choose the editor(s) and then list what
should be documented. Then we can all make a request to write the
appropriate section of ou
Just wanted to throw my hat in the documatation team ring. Is there a
resource as to what needs to be done?
thanks
dfarning
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Until now the following people have "signed in":
bartman007
-nathan
glp (better add myself)
and the following have shown a potential interest:
iam
ggp81
Chz
--
Gregers Petersen, Anthropologist
[EMAIL PROTECTED]
www.wireless-ownership.org
[EMAIL PROTECTED]
__
>> Hello,
>>
>> I am willing to aid in the documentation writing, however I am
>> somwhat limited in my knowledge of OpenWRT. I used WhiteRussian for
>> over a year, WDS mostly, and am now using Kamikaze 707 for STA and
>> WDS. I am definitely willing to help! But I am still learning about
>> Kamik
I'll throw my hat in the ring. I had started restructuring the latex docs in
openwrt/trunk/docs a while back but didn't get too far. Most of the trouble
was centered around the Installation section; I had trouble finding a
satisfactory way to include installation instructions for multiple
pl
Dear Dev-List
In as much as there has been no further comments, regarding my earlier
comments on the subject of an OpenWrt Documentation-Team, I will
tomorrow post the following in the forum:
-
Documentation-Team members wanted
There has during the last months been a slow burning
31 matches
Mail list logo
