<aisa>
It is adding two packages and cleaning up the original package I ported, now that I know more about OpenWrt.
<wolfspraul>
good
<wolfspraul>
that first patch into openwrt-xburst, let me see
<aisa>
but as is my habit, I split each change in the cleanup into its own patch.
<aisa>
I'll bet that one is upstream in trunk.
<aisa>
I didn't check,
<aisa>
but it is a very obvious bugfix.
<wolfspraul>
in general we try to avoid any diff between openwrt-xburst and upstream openwrt that is not absolutely necessary
<wolfspraul>
yes great, then maybe submit it as a patch upstream too
<aisa>
I could post it to OpenWrt devel.
<aisa>
I was just about to ask ;-)
<wolfspraul>
probably a good idea, although I am also not 100% sure what upstreaming workflow the openwrt guys prefer
<aisa>
I'll ask as part of my bug report, those guys have been great to me so far.
<wolfspraul>
just try out see what happens...
<wolfspraul>
ok sounds good
<wolfspraul>
in openwrt-packages, in general we are much more free
<wolfspraul>
because even from the perspective of upstream, that can be seen like an additional 'feed' (=package repository)
<wolfspraul>
so it's a complement to upstream
<wolfspraul>
if one of the packages in openwrt-packages would show up in another feed, we could remove it in openwrt-packages
<wolfspraul>
but since many of them are console tools or NanoNote specific, or at least assume a screen/keyboard etc. I think it might be that openwrt-packages becomes another stable long-term feed for OpenWrt
<wolfspraul>
but in openwrt-xburst, we are trying to manage (i.e. keep small) the diff to upstream at any time
<aisa>
Indeed.  My previous change I'll be shortly reverting and placing somewhere else, so it won't show up as a diff vs upstream.
<aisa>
but I want to first test this permission problem I thought I saw.
<wolfspraul>
sure sure. don't feel kicked around. I am just explaining the current school of thought.
<wolfspraul>
all of this can change too.
<wolfspraul>
mirko made some good suggestions to me recently in a phone call
<aisa>
I've tried to "behave as if" and act as if you were 100% right,
<wolfspraul>
he proposed to delete the 'tracking_trunk' branch in openwrt-xburst, because nobody is active there
<aisa>
taking your advice that I should get to know how Qi works first.
<aisa>
So far it has been a good experience.
<wolfspraul>
people interested in that could take the upstream trunk as a starting point instead, tracking_trunk is just a trap
<wolfspraul>
I agree
<aisa>
I'm not sure about tracking_trunk, yeah.
<wolfspraul>
then he suggested the name 'tracking_backfire' is not ideal, he proposed that 'tracking_backfire' should do just that, i.e. track backfire
<aisa>
it isn't like we'd even use it for the next stable branch.
<wolfspraul>
and there should be a second branch named 'backfire_qi' or so
<wolfspraul>
but then we said we wait with another rename until more pain has built up :-)
<aisa>
:-)
<wolfspraul>
also we need to keep in mind that Milkymist is coming
<wolfspraul>
which I hope over the next year or so we see support for in OpenWrt as well
<wolfspraul>
then the name of the whole project would be wrong 'openwrt-xburst'
<wolfspraul>
but instead of renaming like crazy now disturbing many people, let's wait until there is more need for it
<aisa>
Do you remember the mailing list message about LibreWrt?  And their desire to get FSF sanction as a free distribution?
<wolfspraul>
tracking_trunk can be deleted I think, if there are no objections I think it will just be done soon
<aisa>
I've been wondering if as part of that, or even just for testing,
<aisa>
we might need an x86 branch at some point.
<wolfspraul>
ah that's a long story
<wolfspraul>
the main LibreWrt guy is on this channel, djbclark
<aisa>
I'm ok deleting tracking_trunk, personally.
<aisa>
djbclark: I'd like to brainstorm with you a bit, if you see this.  I'm User:Alanpost on the wiki.
<aisa>
that takes care of that ;-)
<wolfspraul>
if you read between the lines of his last mail or post somewhere (I think it was him), it read some people might not see the need or usefulness of FSF endorsement in the first place
<wolfspraul>
he he
<wolfspraul>
well, between the lines, some of those people are me
<aisa>
heh.
<wolfspraul>
the FSF has great merits in free software, copyright, and the GPL
<wolfspraul>
but in copyleft hardware they have proven to be useless
<wolfspraul>
in fact, counter-productive
<aisa>
dang.  It certainly isn't their primary focus.
<wolfspraul>
they will endorse a product with hidden proprietary software over the same product where the same (!) proprietary software is exposed
<wolfspraul>
since we need to extend the freedoms into the hardware world, that's really bad to us
<wolfspraul>
because the FSF will rather have the things we are trying to free be locked away
<wolfspraul>
but we need it the other way round
<wolfspraul>
we need to expose any proprietary stuff, and write free replacements
<wolfspraul>
OpenWrt is a tool in that process
<wolfspraul>
thank you OpenWrt
<wolfspraul>
no thanks, I don't need you FSF
<aisa>
The bugfix I made to OpenWrt isn't in trunk either.
<aisa>
w00t, I fixed a bug in OpenWrt :-)
<wolfspraul>
having said that, I hope djbclark can become an active distributor of copyleft hardware in the US :-) (www.freedomincluded.com is his site)
<wolfspraul>
so I hope they can finish LibreWrt and start shipping, or maybe now that they realized 'Wrt' is too much of an advertisement for the wrong thing, they rename it first. don't know. ask them.
<wolfspraul>
they are advertising the sale of hidden proprietary software all the time
<wolfspraul>
but since it's hidden they can claim it doesn't exist, even though they know better
<wolfspraul>
pretty amazing
<wolfspraul>
a bit Chinese actually :-)
<wolfspraul>
aisa: bottom line: I focus on OpenWrt, OpenWrt is great. LibreWrt solves a strange problem from my perspective, although the result will still be free software, and run on the NanoNote, so fine.
<wolfspraul>
is anyone HURD?
<aisa>
Having worked with OpenWrt now, I really understand why you like it.
<aisa>
It is amazing.
<aisa>
I sent the patch to openwrt-devel.
<wolfspraul>
congratulations!
<wolfspraul>
if you are already at the level that you can provide actual fixes to them that would be awesome
<wolfspraul>
let's see...
<wolfspraul>
aisa: hmm, looking at the patch, you are removing the redirection of stderr to /dev/null ?
<wolfspraul>
and that makes it ignore the missing directory?
<wolfspraul>
-Â Â Â Â Â Â @if [ -d "$(2)" -a "$$$$(ls $(2) 2>/dev/null | wc -l)" -gt 0 ]; then \
<wolfspraul>
+Â Â Â Â Â Â @if [ -d "$(2)" -a "$$$$(ls $(2) | wc -l)" -gt 0 ]; then \
<wolfspraul>
(for reference)
<aisa>
it sends the error, which happens on stderr, to /dev/null.
<aisa>
so, I'm adding it.
<aisa>
did I get the patch backwards?
<aisa>
dur.
<wolfspraul>
ah :-)
<wolfspraul>
that explains it :-)
<wolfspraul>
redirecting stderr to /dev/null also isn't the nicest thing to do. why not add a separate check whether the directory exists?
<aisa>
I think that is the better plan,
<wolfspraul>
well, let's see what feedback they give...
<aisa>
indeed.
<aisa>
ok, corrected patch sent.
<aisa>
thank you for catching that!
<wolfspraul>
if you still redirect I wouldn't be surprised if they don't like it
<wolfspraul>
I wouldn't
<wolfspraul>
I'm always amazed how well this stderr and stdout stuff works
<wolfspraul>
sometimes I run a high-level command on a server, and it fails
<wolfspraul>
then I think "oh my god, how long will it take until I figured out where in the system the error comes from"
<wolfspraul>
but there it is... from deep inside the scripting and utilities magic... reported all the way through to me
<wolfspraul>
(sometimes, I admit, but when it works it's really nice)
<wolfspraul>
but that only works if people have some discipline in not silencing stdout/stderr, but keeping them untouched so the entire stack can benefit
<wolfspraul>
if I assume I'm the topmost script/caller I admit I also often just silence it, to get my job done
<wolfspraul>
anyway
<aisa>
Indeed.  If I understood better the syntax being used right there, I'd do if [ -f $(1) ]; ls $(1)
<aisa>
or something like it.
<aisa>
I think it is good to start with a solution that can be clearly improved on, it gives someone an opportunity to teach :-)
<aisa>
Also, I copied that strategy from elsewhere in the code.
<wolfspraul>
he, yeah
<wolfspraul>
I also don't know right away how to get the check inserted
<wolfspraul>
I'm not sure what the latest guidelines are about author reachability, email addresses etc.
<wolfspraul>
in some (rare but important) cases the ability to reach many authors of whatever project quickly and effectively can be very helpful
<aisa>
ah, indeed.
<aisa>
I though that having my name there would be tied to my commit access.
<aisa>
and of course, if my e-mail address changes, I can update in one place.
<wolfspraul>
sure it may be
<aisa>
however, this is only true so long as the code is stored at this repository.
<aisa>
and being free software,
<aisa>
it may well get copied around.
<wolfspraul>
but like I said "quickly and effectively"
<wolfspraul>
correct
<wolfspraul>
I don't know what the latest state-of-the-art there is.
<wolfspraul>
but just "Alan Post" is probably not ideal
<aisa>
right.
<aisa>
let me think the night on this one.
<wolfspraul>
I always check with the Linux kernel, they tend to have the most verbose and thought through policies.
<aisa>
It could be best to have an AUTHORS file,
<aisa>
with many ways of contacting.
<aisa>
or it could be better to add an e-mail to every header.
<aisa>
ah, indeed.
<aisa>
wonderful idea.
<wolfspraul>
about why -d doesn't work..
<wolfspraul>
do you know why there are 4 $$$$ ?
<wolfspraul>
it isn't immediately obvious to me
<aisa>
I don't know, other than two escapes.
<wolfspraul>
maybe there need to be 4 $$$$ in the -d also ? :-)
<wolfspraul>
just guessing around...
<aisa>
ha!  right.
<wolfspraul>
well not sure
<aisa>
Hey, it is late here for me, and now that I've made these commits, I have accomplished my goal for the evening.
<aisa>
I'm going to go to sleep.
<wolfspraul>
after -d is a test after -a (stands for 'and', right) is an expression
<aisa>
I believe that is all true.
<wolfspraul>
ok 'night
<aisa>
co'o
<wpwrak>
i think that should be ` ... ` instead of $(...)
<wpwrak>
or wait, no, i'm confusing this with $(shell )
<wpwrak>
strange then
<wpwrak>
ah no. makes sense. use [ X ] && [ Y ] instead of [ X -a Y ] :)
<wolfspraul>
oh the -a will not abort after the left part failed?
<wolfspraul>
I didn't know that...
<wolfspraul>
I would have thought every language does that
<wpwrak>
the -a can't. you're invoking "test" with the arguments already expanded. the error happens in the expansion.
<wpwrak>
on the other hand, with &&, the shell sees that the left-hand side is false and doesn't expand the right-hand side
<wolfspraul>
so the fixed line is? @if [ -d "$(2)" ] && [ "$$$$(ls $(2) 2>/dev/null | wc -l)" -gt 0 ]; then \
<wolfspraul>
(too lazy to try this out)
<wolfspraul>
wpwrak: can I delete s.try on fidelio:/home/schhist ?
<wpwrak>
me too ;-)Â Â looks good excelt that you don't need the 2>/dev/null
<wolfspraul>
ah sure
<wolfspraul>
aisa: try this one @if [ -d "$(2)" ] && [ "$$$$(ls $(2) | wc -l)" -gt 0 ]; then \
<wpwrak>
or, much simpler [ ! -z `ls $(2)` ]
<wolfspraul>
(hope this won't wake you up, but I cannot imagine anyone configuring their irc client to connect nick mentioning to an alarm bell or such :-))
<wpwrak>
(for the 2nd expression. still need the first)
<kyak>
i've commited it for now, but it still requires some polishing (it builds only with "-static")
<kyak>
also the package size is ~11 Mb, i think some files can be thrown away
<kyak>
but it's good to test
<wolfspraul>
nice, congratulations!
<kyak>
thanks, but as i said, it was already there :)
<wolfspraul>
sorry can't follow now
<wolfspraul>
it was there? where?
<kyak>
binutils, gmp were already ported; mpfr is a part of toolchain, i only packaged it; uClibc is in toolchain; gcc was also ported for x86, i just had to modify it
<wolfspraul>
ah OK, now I got it :-)
<wolfspraul>
sorry..., lack of overview
<kyak>
it is amazingly slow, btw.. during usual ./configure at takes ~1-2 seconds for each test line to appear
<wolfspraul>
hmm
<wolfspraul>
interesting
<kyak>
for example: the 'patch' utility takes 0m 06.24s for configure, 0m 02.78s for make on my host.. and on Ben configure takes 3m 10.02s and make is 5m 49.95s
<kyak>
i guess i have to throw away the idea of building kernel and rootfs on Ben :)
<wolfspraul>
that's a pretty radical idea anyway
<wolfspraul>
I think gcc is nice to have, in a number of cases
<wolfspraul>
and also patch, make, etc.
<wolfspraul>
but to build the rootfs? not sure...
<wolfspraul>
but hey, who knows. maybe performance can be improved? don't know.
<kyak>
now, it's just for fun
<wolfspraul>
I'm wondering how this was when we had Pentium-90 machines
<kyak>
besides, would be cool to state to someone that Ben is self-sufficient and can be used to build a firmware for itself
<wolfspraul>
I think I remember having had 16 and 33 mhz 386 computers.
<wolfspraul>
yes agree
<kyak>
i rememeber i built linux kernel on AMD K6-2 (450 Mhz)
<kyak>
it took couple of days.. i wonder if that COU is fast than that of Ben
<kyak>
would be good to hae an understanding what is the analogue of our JZ4740 CPU in x86 world
<kyak>
like, it is PEntium-I? or II?
<wolfspraul>
hmm, not sure
<wolfspraul>
there are many differences, in instruction set, pipeline/caching architecture, bus speed and width
<wolfspraul>
best is probably to just run the same load and then compare, like building patch :-)
<kyak>
yep.. now to find such old trash :)
<kyak>
i wonder if this can be emulated in virtual machine
<tuxbrain>
kyak: time ago there was a benchmark test with pentium openmoko nanonote and pentiumII search the archives
<tuxbrain>
kiak my mistake it was other procesors but a benchmark any way it was called "A few benchmarks for the Nanonote" from Delbert Franz at May 4th
<kyak>
tuxbrain: thanks for the hint
<kyak>
yes, nice post from Delbert Franz
<kyak>
as i see, Ben is 2 to 10 times slower than a PC of Pentium II class
<B_Lizzard>
I just fixed me a nice gtk-1.2 theme
<B_Lizzard>
Next up, implementing applications
<wpwrak>
kyak: maybe try to use uSD instead of NAND or vice versa. also, adding swap may help. it allows the kernel to get rid of idle pages, so it can do better caching.
<wpwrak>
wolfspraul: on those older systems, we also had leaner tools. e.g., gcc 1.something ;-)
<wpwrak>
well, on the 386. on the pentium, it was already gcc 2 or such. i remember that going from gcc 1 to 2 was quite a bit of pain, because it was so slow.
<wolfspraul>
the first version I used was 2.95
<wolfspraul>
before that only Microsoft compilers
<wolfspraul>
or Borland before that :-)
<wolfspraul>
wpwrak: did you get my reply about the patent policy?
<wolfspraul>
I think we should just upload the text to that page, then we can go from there
<wolfspraul>
it's a wiki :-)
<kristianpaul>
xiangfu: i'm confused, i tough there was a target system for SIE in xburst openwrt?..
<wolfspraul>
he
<wolfspraul>
the hunt for the nonexisting SIE target maintainer has started
<kristianpaul>
:p
<wolfspraul>
kristianpaul: maybe you can say some magic words in Spanish to Carlos, and he will switch from massive extremely hacky patches that are sent around as attachments in private mails to something a bit more collaboration friendly :-)
<wolfspraul>
we have patches flying aroud that brutally just comment out stuff in the Ben sources, and replace it with SIE stuff. If we would 'apply' those, the Ben build would, small side-effect, completely break right away
<wolfspraul>
so big surprise - the patches cannot be applied :-)
<wolfspraul>
first step would be to stop patching (breaking) Ben sources, and instead have a few dedicated SIE source files where it's necessary
<wpwrak>
wolfspraul: (policy) i saw that i have mail. will read it over breakfast :)
<wolfspraul>
oh sure take your time
<wolfspraul>
your text is the best that was written down on that subject since Qi was started
<wolfspraul>
we don't seem to have the people (me included) that have enough motivation to try to tame that mess with a good text
<wolfspraul>
look at the patent-free page :-)
<wolfspraul>
that's as much as we could squeeze out from our results-oriented minds...
<kristianpaul>
wolfspraul: so the image my SIE board have came up from a Carlos private mail?.. :/
<wpwrak>
wolfspraul: (magic words) kristianpaul said that he doesn't know carlos. so he may not date to use "boludo", which is i think the word you're looking for ;-) (well, i'm not sure they have it in colombia)
<wolfspraul>
they know each other a bit, I mean we all hung out at the Campus Party together
<kristianpaul>
wpwrak: we dont but there are some similars tought
<wolfspraul>
kristianpaul: I don't know
<wolfspraul>
the sources are all there
<wpwrak>
*grin*
<wolfspraul>
there is not that much missing - BUT, the big force of gravity that would clean this up and make it easily accessible to others does not exist
<wolfspraul>
this is also not helped by very few people having the board
<wolfspraul>
95% of which are in Colombia
<kristianpaul>
.D
<wolfspraul>
it's definitely not the commit rights into openwrt-xburst that stops it
<kristianpaul>
i have a word for that is "mess"
<wolfspraul>
wpwrak: yeah that page is great, isn't it?
<wolfspraul>
I think Jon wrote it after some lengthy discussions with me.
<kristianpaul>
patent-free great :)
<wolfspraul>
we were both exhausted. in my case that translated to 'sleep', in his case I guess he managed to squeeze this out of his fingers before getting drunk or so.
<wolfspraul>
:-)
<wpwrak>
wolfspraul: it's very to the point on the motivation. alas, a bit light on the practical implications
<wolfspraul>
yeah come on. time is limited. I'm no lawyer, cannot charge anybody for my words.
<wolfspraul>
:-)
<wolfspraul>
anyway it's the best/most Qi has managed to write up on the subject so far
<wolfspraul>
maybe you can leave it as an intro
<wolfspraul>
I still like it.
<wpwrak>
hmm, its scope is broader than the policy. the policy is only about avoiding trouble with other people's patents.
<wpwrak>
"patent-free" is mainly about the use of patents on the qi-hw side
<wolfspraul>
does this mean the policy will get even longer before it says what the current text already says?
<wolfspraul>
(just joking)
<wolfspraul>
you asked for my feedback. my feedback is the text is great, add it to that page, and if you ask me - leave the current 2 lines on that page as an intro or somehow merged into your text somewhere.
<wpwrak>
it woud have to get longer to cover that stuff at the same level of detail as well :-(
<wolfspraul>
let's just upload it now, merge with the existing 2 lines in a smart way, and done
<wolfspraul>
we can polish / extend this over time
<wolfspraul>
the important thing is to clearly communicate to newcomers or interested people what we collectively believe in
<wpwrak>
but i think it's two completely different audiences anyway. one is for those who wonder if they/we should patent something. the other is something anyone placing public content on qi-hw should be aware of
<wolfspraul>
could be even more motivations to read this
<wolfspraul>
"virtual warfare over an artificial problem"
<wolfspraul>
he :-)
<wpwrak>
it's more like patent philosophy vs. appropriate use of the public qi-hw infrastructure
<kristianpaul>
arggg carlos !!
<kristianpaul>
(chatting privatelly)
<wpwrak>
so i wouldn't mix the two. too distant. the patent-free text is for the legislative, the policy for the executive. don't make the cops read works contemplating the human condition. at least not on the job ;-)
<wpwrak>
(virtual warfare) that's a nice one :)
<wolfspraul>
wpwrak: well ok let's translate to reality. the policy needs to go into the wiki. if you want a separate page just create one.
<wolfspraul>
let's just get this text online then it can start its life.
<wolfspraul>
no?
<wpwrak>
alright. i can put a link to patent-free. something in the sense of "we don't like patents [link] but we have to play by the rules."
<wolfspraul>
basically you say one text is about what we are trying to achieve (around patents). the other one is about how we are going to achieve it.
<wolfspraul>
what we are trying to achieve is to have the strongest, highest performing, most innovative, yet 100% patent-free hardware
<wolfspraul>
and how we are going to achieve it is documented in the patent policy
<wolfspraul>
correct?
<wpwrak>
even less. patent-free is a little about what we're trying to achieve and more about what part we plan to play in the patent system.
<wolfspraul>
yeah
<wolfspraul>
none
<wolfspraul>
:-)
<wpwrak>
the policy is about what rules apply for content on qi-hw.
<wolfspraul>
just let us know what we need to take out, and for how long
<wolfspraul>
we focus on innovations elsewhere
<wpwrak>
the patent policy doesn't cover areas like whether we should apply for patent, how we should disseminate our prior art, how we should respond to patents covering out prior art, how else we can help fight patents, and so on.
<wolfspraul>
fair enough
<wpwrak>
on the other hand, the policy could be extended to cover other areas of IP. it's basically the guideslines for how a contributor to qi-hw should behave to avoid getting others (qi-hw, distributors) in trouble.
<wolfspraul>
we would need community members that are passionate about these things and start acting on those issues
<wolfspraul>
afaik we don't have them right now
<wolfspraul>
well I think any text needs to be reasonably specific otherwise we are wasting everybodys time
<wolfspraul>
so it should be about 'patents', and about 'mp3/h.264/mpeg4', just as you did
<wolfspraul>
your text is great
<wolfspraul>
why don't you just upload it then we have a base...
<wpwrak>
one is clearly for activists. those who choose to simply ignore patents as much as possible don't need to read "patent-free" and any proactive recommendations that may get added to it.
<wpwrak>
the other is for everyone. road rules. spitting on the street allowed in our village, but please use a toilet for the rest.
<wpwrak>
(my text) there are a few questions in there, in square brackets. any comments on these ?
<wolfspraul>
oh
<wolfspraul>
:-)
<wolfspraul>
I need some valium or so to actually read every word.
<wpwrak>
particularly, the one on "planet"
<wpwrak>
the others are more editorial
<wolfspraul>
planet?
<wolfspraul>
one sec
<wpwrak>
yeah, writing that stuff does get you angry, doesn't it :) i just HAD to write that last section to let off steam :)
<kristianpaul>
wolfspraul: i giveup with carlos, sorry :)
<wpwrak>
kristianpaul: let us know the words you used :)
<kristianpaul>
wpwrak: (pues bueno..)
<kristianpaul>
chao !
<kristianpaul>
thats it ;)
<wolfspraul>
kristianpaul: what does that mean?
<wpwrak>
i think "shrug. bye then"
<kristianpaul>
;)
<wolfspraul>
the planet...
<wolfspraul>
well since the policy is for people to guide them on actions, ok, maybe it's similar to irc
<wolfspraul>
if you are hosting a blog that is syndicated in the planet, and you are posting instructions that infringe, the qi-hardware web admins need to censor your post from the archives
<wolfspraul>
if you do it frequently/all the time, the qi web admins may remove your blog from the planet
<wpwrak>
wolfspraul: (planet) the thing is, planet re-publishes content of others who may not even know that we're using their stuff.
<wpwrak>
wolfspraul: okay, so edit after the fact
<wpwrak>
that works
<wolfspraul>
btw, the planet html page itself has no archive, but entries are visible for 1-2 months or so
<wolfspraul>
but then we have 2 mailing lists (rss2email), which also have archives
<wolfspraul>
but anyway
<wolfspraul>
that is all the problem of the qi admins
<wolfspraul>
because we want to say to manufacturers or distributors that we are keeping our technology in such a state that if those guys manufacture or sell the resulting devices, the chances of someone claiming infringement of their patents are very low
<wolfspraul>
wpwrak: of course, same on the list or irc
<wolfspraul>
we still have the concept of freedom of speech
<wolfspraul>
that's a 'passing' conversation
<wolfspraul>
the difference is if someone archives that, and keeps it available for others to reuse
<wolfspraul>
that someone cannot just claim 'freedom of speech' anything, in fact it wasn't even that someone who spoke
<wolfspraul>
so why keep the archives?
<wolfspraul>
TO INFRINGE!
<wolfspraul>
:-)
<wolfspraul>
kristianpaul: well I tried to understand what you asked for, and why the conversation ended.
<wpwrak>
so you'd say also the mailing list should be treated as being as ephemeral as IRC ?
<wolfspraul>
and how can we now help you?
<wpwrak>
or a little less ?
<wolfspraul>
ephemeral? wait I need to look this up...
<wpwrak>
volatile, not lasting
<wpwrak>
"vergaenglich" :)
<wolfspraul>
hmm
<wolfspraul>
from the perspective of a patent owner there is no difference between an irc log and a mailing list archive
<wolfspraul>
it's text, hosted on a server, server is run/paid for by abc
<kristianpaul>
wolfspraul: iwas a talk about, why you this thet should do it and not you..
<kristianpaul>
s/this/think
<kristianpaul>
s/thet/they
<wpwrak>
good that the irc logs are being archived. that can serve as proof for due diligence ;-)
<wolfspraul>
if someone posts a mail to the mailing list, with instructions/links, then the qi admins have to remove this mail, or parts of it, from the archives
<wolfspraul>
that's our service to the copyleft hardware community, to keep the copyleft hardware manufacturable and sellable with small risk of successful patent infringement claims
<wolfspraul>
I wouldn't think that makes the mailing list 'ephemeral'
<wolfspraul>
the issue is about WHAT you post
<wolfspraul>
I mean we would also remove spam
<wolfspraul>
and we also remove stuff that will make it possible for patent holders to launch a successful patent infringement claim
<wpwrak>
mailing lists get replicated more than irc goes. e.g., each subscriber implicitly gets a copy, gmane may have qi-hw, etc.
<wolfspraul>
no problem
<wolfspraul>
gmane is someone else anyway
<wolfspraul>
the issue is only about what is hosted on qi-hardware.com servers
<wolfspraul>
the copies that are sent to people don't matter either
<wolfspraul>
it is an undue burden that the qi admins would have to review every mail before it is being sent to the list
<wolfspraul>
kristianpaul: ok but what is your problem, and how will you solve it now?
<wpwrak>
that's one thing. violation of usage policy. but can the usage policy itself allow such things then ?
<wolfspraul>
hmm
<wolfspraul>
puh
<wpwrak>
:)
<wolfspraul>
you have to drill into every last corner
<wolfspraul>
I don't know.
<kristianpaul>
wolfspraul: was pity, (missing password) so i think i know what do to to reflash the SIE and make some changes i need to the FPGA
<wolfspraul>
I don't think we need to, or even would have the authority to, restrict someones rights to speak freely.
<wpwrak>
/n the_sadist (-:C
<wolfspraul>
they will just do it.
<wolfspraul>
the policy doesn't need to pickup this fight
<wolfspraul>
it can jsut say "not tolerated and will be removed from archives"
<wolfspraul>
the policy neither needs to encourage people to use the list to distribute infringement stuff, nor does it need to install any sort of gag order, which couldn't be enforced anyway (we already say we remove such stuff from the archives)
<wpwrak>
hmm. i can see how to put the cya angle. but it would then fall short of giving people specific guidelines for what they should and shouldn't do.
<wpwrak>
hmm
<wolfspraul>
ok let's talk about friendliness then
<wolfspraul>
if you want to be friendly to the project, do not use project resources to spread information about how to get mp3 to play, mpeg4, h.264
<wolfspraul>
it doesn't help us
<wpwrak>
alright. that's good.
<wolfspraul>
because we cannot include such functionality anyway, and in fact we need to constantly cleanup behind out chatty community members :-)
<wolfspraul>
behind our
<wolfspraul>
kristianpaul: do you think you are able to create the full image you have on your SIE from source?
<wolfspraul>
or is it entirely undocumented/messy?
<kristianpaul>
well not so messy atl all
<kristianpaul>
wolfspraul: yes sure, the source actually is same Ben image :)
<kristianpaul>
replace root_fs and thats it
<kristianpaul>
and uboot too, but i dont need reflash uboot
<wolfspraul>
the kernel is not the same
<kristianpaul>
i think is, or carlos said that
<wolfspraul>
ok I'm a software guy, when I say 'same' I mean md5sum(ben_uImage) == md5sum(sie_uImage)
<kristianpaul>
hehe
<wolfspraul>
I have massive doubts that that is the case.
<wolfspraul>
massive as in 99.99999%
<wolfspraul>
the only .000001% only to save Carlos face :-)
<wolfspraul>
but seriously, no, there must be changes
<wolfspraul>
so if you reflash, be careful
<wolfspraul>
you may end up with a system that won't work anymore, and then getting it back to work may be hard
<kristianpaul>
well any way if carlos desided to move to something more colabortive will be SIE as a fork from Ben as in sofware and hardware (wich is right now)
<wolfspraul>
I think the SIE target maintainer (in OpenWrt) needs to come from outside of Bogota
<wpwrak>
wouldn't having all the SIE stuff nicely out in the open be a prerequisite for selling it to others than carlos' group ? :)
<kristianpaul>
we are chatting again about create a project in indefero
<wolfspraul>
wpwrak: it is all there, just messy (imo)
<wolfspraul>
it's not about lack of motivation to do so, it's lack of skills
<kristianpaul>
idependent from uboot,linux,root fs  frm the current one
<kristianpaul>
wolfspraul: (skills) agred
<wpwrak>
ah, that's harder. but it also seems to be in part poor practice - you mentioned patches sent by private mail and such.
<kristianpaul>
carlos students are so vage mostly so nobody  besides carlos to support sofware side.
<wolfspraul>
sure
<kristianpaul>
thast why i ends in privatelly mails to qi people ;)
<wolfspraul>
wpwrak: yes that too.
<kristianpaul>
s/i/he
<wolfspraul>
the pieces are all there
<wolfspraul>
but not in one place, not clean
<wolfspraul>
also there are too few boards now
<wolfspraul>
my hope was that David would get 5 or so, and me another 5 or so
<kristianpaul>
wolfspraul: sure not in Bogota for sure
<kristianpaul>
see what i dont live there ;)
<wolfspraul>
there are plenty of people that are interested and able to cleanup the software (which is not that much work since the Ben SW is in great shape, I think)
<wpwrak>
student work is generally volatile :) PhD students have a long-term interest but all the rest is hard to integrate into such projects. occasionally, someone has good enough skills to get started quickly and it thorough enough to make something stick, but it's not very common
<wolfspraul>
but now I have 0 boards, and David has 1
<kristianpaul>
all the hacks are in the curret nn-usb-fpga
<wolfspraul>
because the V2 yields were a little lower than hoped, and Carlos students had priority (and paid)
<wolfspraul>
so I cannot help with the maintainer thing either
<wolfspraul>
with 0 boards :-)
<wolfspraul>
and David has 1
<wolfspraul>
that won't change until a V3 run which may be months out
<kristianpaul>
but more features for SIE will come, so it shows definelly that SIE need a new project :)
<kristianpaul>
software porject*
<wpwrak>
adam has given up on fixing the remaining boards ?
<kristianpaul>
larsc: xiangfu openwrt tarjets can habdle different uboots and linux images isnt?
<kristianpaul>
targets*
<wolfspraul>
to put my words into perspective a bit, I may be too hash
<wolfspraul>
harsh
<wolfspraul>
Carlos has done a great job, all software exists, and, it is based on the Ben software which imo is in excellent shape
<wolfspraul>
my estimate is it would take a really skilled sw guy maybe 2 weeks to clean it all up in OpenWrt, especially if that person had some prior knowledge of OpenWrt
<kristianpaul>
ahap
<kristianpaul>
indeed
<wolfspraul>
but for that this person would need the board, and all patches/hacks/scripts/whatnot
<wolfspraul>
then 2 weeks, then all is perfect
<wolfspraul>
but this step will, again imo, not happen in Bogota
<wolfspraul>
and me and David have too few boards
<wolfspraul>
so we are a little stuck on this
<wolfspraul>
eventually we find a way out :-)
<wolfspraul>
wpwrak: yes Adam has stopped, because I asked him to. it's about cost. right after the run 19 boards had problems.
<larsc>
best would be to get the SIE platform patch into upstream linux
<wolfspraul>
he fixed 9 of them, it got slower and slower.
<kristianpaul>
the issues i see, is openwrt able to build system that can handle different kernel confifuration even for uboot, and no afect current ben target?
<wolfspraul>
kristianpaul: worst case you can have a uboot-sie package
<kristianpaul>
larsc: not posible yet, well or think so,  as more features are coming
<wolfspraul>
maybe even as a diff on top of the uboot-xburst? :-) don't know how flexible OpenWrt is
<wolfspraul>
wpwrak: so if Adam would continue fixing those 10 boards, those days would eat into Milkymist One RC2
<kristianpaul>
larsc: i think i wroing in the last, coming features dont care isnt?
<wolfspraul>
and we have 27C3 coming up
<wolfspraul>
I cannot take the risk. Adam already spent 5 days or so fixing the first 9 boards, and was quite exhausted at the end. The last 2 days only 1 or 2 came out of the fixing.
<larsc>
kristianpaul: well those could be added in later patches
<wolfspraul>
the remaining 10 would need serious root cause searching, to prepare for the next run. So I'm sitting on them for that purpose.
<larsc>
code is not frozen once upstream
<wpwrak>
wolfspraul: (adam) okay, so he's already saturated with more important stuff. makes sense then.
<wolfspraul>
wpwrak: yes. it's just risky with 27c3 coming.
<wolfspraul>
I cannot let down Sebastien on this.
<wolfspraul>
and there will always be surprises.
<wolfspraul>
it's already tight
<wolfspraul>
I need to move everything out of the way for that now.
<wolfspraul>
once the RC2 boards are made maybe Adam can go back a few days and try to fix a few more SIE
<wolfspraul>
maybe late November even? don't know
<wolfspraul>
I need to get RC2 done first
<kristianpaul>
wolfspraul: when RC2 should be done?
<wolfspraul>
calculate backwards from 27C3
<kristianpaul>
wolfspraul: and the boards will be sell in 27C3?
<wolfspraul>
27C3 starts Dec 27
<kristianpaul>
or pre-oder?
<wolfspraul>
Bearstech offered their booth
<kristianpaul>
i'm just curios
<wolfspraul>
you don't want to try shipping stuff to europe on Dec 21 or so
<kristianpaul>
hehe
<wolfspraul>
so they need to leave Asia no later than first week of December
<wolfspraul>
and they need to be tested
<wolfspraul>
(going backwards)
<wolfspraul>
and we need the jtag/serial cables
<wolfspraul>
and power adapters
<wolfspraul>
and boxes
<wpwrak>
you have 2-3 weeks to finish the design and order the production run :)
<wolfspraul>
we need to be careful about customs (first shipment of anything is always risky)
<wolfspraul>
the SMT date needs to be scheduled
<wpwrak>
pcb have to be made
<wolfspraul>
the PCBs need to be ordered, made, received, tested
<wpwrak>
parts need to be ordered
<wolfspraul>
before that the layout house needs to go back work their way through our change list
<wolfspraul>
it's October 9 now
<wolfspraul>
does Adam have time to fix a few more SIE right now?
<wolfspraul>
no!
<wpwrak>
maybe if he can work negative hours on them :)
<wolfspraul>
Adam may also get sick, or, big surprise, need a few days off somewhere
<wolfspraul>
sometimes vendors make mistakes
<wolfspraul>
ship the wrong thing
<wolfspraul>
or apply the wrong production process, which leads to unusable pcbs
<wolfspraul>
or or or
<wpwrak>
let's hope there be no bad shipments. your schedule doesn't supprt that error or margin.
<wpwrak>
err, margin of error :)
<wolfspraul>
wpwrak: I think it's still OK
<wolfspraul>
it's the second run
<wolfspraul>
number of changes is manageable
<wolfspraul>
many parts still in stock
<wpwrak>
okay if you order next week. are you that close ?
<wolfspraul>
but I agree this is tight and I explain it all to explain why I really cannot risk loosing days right now over SIE fixes
<wpwrak>
also, how about the case ?
<wolfspraul>
no case, gave up on that for 27C3
<wolfspraul>
cannot make it
<wpwrak>
sure sure. "adam is busy elsewhere" explains enough ;-)
<wolfspraul>
well I like to explain the whole picture
<wolfspraul>
maybe someone else wants to manufacture 10 or 20 SIE?
<wpwrak>
(case) maybe find some off-the shelf case that's not too horrible
<wolfspraul>
I could probably supply such a run with a lot of helpful material, components, etc.
<wpwrak>
(sie) golden delicious ? :)
<wolfspraul>
I will try to sneak in a few days of SIE fixing (out of those 10), when I feel those days are not on the Milkymist critical path
<wolfspraul>
the moment I have such days I will try to 'make' another 2-3 fully functional SIE from the 10
<wolfspraul>
but right now I feel the Milkymist critical path everywhere :-)
<tuxbrain>
mmm, I can ask about the cost of doing 20 Sie boards here..., maybe I need help on the right files to send to the manufacturer, what components would you sendme wolfgang and what I have to source locally
<wpwrak>
aisa: btw, i think the  ls $(2)  is still inconsistent with the  -d "$(2)" . if $(2) needs quoting at all, then it would need quoting also in the ls. but then, i don't know if it actually needs this or not
<wpwrak>
(as request for comments for now. everybody can play policy maker here :)
<aisa>
testing now, but I may have to leave before I can finish.
<wpwrak>
aisa: not sure what degree of escaping you need, with make adding one layer of indirection. you'll have to try and (maybe) err :)
<kristianpaul>
tuxbrain: but as you said just wolfgang know what he will send you :)
<aisa>
right, #1 didn't work.
<tuxbrain>
ok I will ask when he reconnects
<aisa>
trying: '$(2)'
<tuxbrain>
wpwrak: reading page
<aisa>
that seems to have worked.
<aisa>
I suppose I should really test with "patches with space"
<wpwrak>
yes :)
<aisa>
because thinking about it, '$(2)' shouldn't work.
<aisa>
man, I thought I knew sh and makefile better than I do...
<aisa>
actually, it should.  $(2) is expanded by make.
<aisa>
and that can be single-quoted in sh.
<aisa>
not that it works...
<tuxbrain>
wpwrak: I think also worth to mention about pictures in wiki not totally free, any picture with non-comercial clause, must be avoided too
<wpwrak>
the $$$$ hints at there being yet another level. at least i don't normally see that sort of thing.
<wpwrak>
tuxbrain: so that would be the extension into copyrighted material.
<tuxbrain>
yeah but as you put the emepetres examples I think this example also need to be mentioned
<wpwrak>
tuxbrain: not sure if we should cram everything into one document (that would then be on IP, not just patents), or treat this separately
<tuxbrain>
ok
<tuxbrain>
underetand your poing
<tuxbrain>
point
<tuxbrain>
understand
<wpwrak>
tuxbrain: i would lean towards combining things too, but i'm not sure if i understand the matter well enough to not overlook some subtle differences :)
<tuxbrain>
wow that nap and your text is a bad combination for my finguers
<aisa>
wpwrak: I've got to go for today, but I'm testing now and will figure it out.
<aisa>
thank you for reminding me.
<wpwrak>
let's do it like this: for now, i'll just cover patents. i'll mention that general IP (copyright, trademarks, etc.) is similar and that it may or may not make sense to include it, too.
<wpwrak>
aisa: always happy to heckle ;-)
<wpwrak>
tuxbrain: i'm also a little afraid that, if i make it too long, nobody will read it ;-)
<tuxbrain>
a more agressive summary should be we piss of on pattent stuff, we want this fucking crap as far away from us as posible.
<wpwrak>
two reasons: a) patent-free has a different focus. it describes what we do with OUR original ideas, while the patent policy describes what we do with idea others have removed from the public domain.
<wpwrak>
b) the patent-free page may get extended, which would make the thing unwieldy.
<tuxbrain>
ok I think my sentence include both cases :)
<tuxbrain>
ok again understand your point
<wpwrak>
after all, the goal is to have guidelines people will actually follow. not a scholarly work on theory and practice of intellectual property legalese, to be read by lawyers only.
<wpwrak>
(aggressive summary) yeah. i'm thinking of finding a way to put "we prefer lawyers to be starved and too weak to fight, not bursting with confidence and eager to make the world quiver before their powers" somewhere.
<wpwrak>
(piss of on) it's just "piss on" :)
<wpwrak>
alas, that's not an option. well, if YOU decide not to worry about patents anymore, i'm sure you can be accommodated ;-)
<tuxbrain>
I hope one day we can have a lawyer in the community that can take care of this stuff, until now your guide is the best think I read about , so go for it
<wpwrak>
it may just be a somewhat hazardous decision
<tuxbrain>
I don't say I dont take care, I want them far away from me so it implies I take care of they doesn't being close :P
<tuxbrain>
time to time I still had nighmares of nanos stopped at customs, brrrrr, terrifing
<rafa>
wpwrak: I really do not like the whole thing. I need a while to read and read to understand well.. and still.. it is going deeper and deeper because just in few places around the world could have problems with that, and then the rest of us needs to follow some guidelines, ways, or whatever.
<wpwrak>
rafa: alas, the places where you have trouble are those where they project can get money. if the main market was south america, you'd see the same thing happen here. IP laws are fairly global :-(
<rafa>
wpwrak: from time to time that all sucks for me and I feel that it is really a annoying thing which is not directly related with the rest of users/people. it is just one thing useful for qi and resellers.. which does both worlds hard to live together. I mean, I think that patents sucks of course, and if mp4/mp3.. whatever does
<wpwrak>
rafa: without qi-hw and resellers, there are no bens and no users. so it pretty much does affect them ...
<rafa>
problems to nice projects like qi and family then I really would try to help.. but it is going so deep to me understand why I should follow some things to collaborate
<rafa>
wpwrak: without qi and resellers there are no bens: I understand that.. but still, it is not my fault and that will not affect users at all surely :(
<wpwrak>
rafa: well, what can i say. these threats are not imagined. this sort of confiscation at customs has happened to openmoko.
<wpwrak>
rafa: (well, to one of their resellers - because openmoko had codecs on the device)
<wpwrak>
rafa: you could also view this as an opportunity - each time you avoid using a patent, you shrink the market for them :)
<wpwrak>
rafa: particularly if avoiding the patent means that you coe up with an alternative that achieves the same result. e.g., think of GIF. that patent was completely devalued by the avoidance of GIF files and the development of alternative and better file formats.
<rafa>
wpwrak: :( yeah.. but I just do easy tasks just for fun.. and nobody is going to convert all his/her mp3 files to ogg.. still if here in this channel there 1 to 5 guys who did that.. the rest will not do that, just to give a bad example
<rafa>
there 1 to 5 = there are maybe 1 to 5
<tuxbrain>
has all his mp3 converted to ogg
<rafa>
1 guy so far :)
<rafa>
well, maybe more, just 1 who already confirmed it :)
<tuxbrain>
as easy as one order of a shell
<rafa>
tuxbrain: yes of course, becuase all of the mp3 users have come surely from internet they will need to put that order into crontab or something similar
<rafa>
because they will get more mp3 from time to time
<tuxbrain>
wpwrak: it's not copyright infringiment is a tribute :) I think I will record this one day heheeheh or at least my nightmares now will have a new backgroud music  "we don't want no confiscations... papara papapa papara we"
<tuxbrain>
c u later, guys, rafa, I see you a little low today, common!!! it is mostly a game, some of us has bet money others bet time, we are just finding strategies to win, all toguether, we are a team, users, developers, resellers and manufacturers don't give up in the boring part of the game, we will take care of it , just play the part you like also you are not tied to play if you don't find it fun, but be sure I will miss you :), btw send me the ogv pl
<tuxbrain>
ayer before you leave :P
<kyak>
wpwrak: thanks for the hints; of course i have swap enabled on uSD, and i also doubt that it's drive performance that is a bottle neck
<kyak>
though you are right, the speed of NAND could've been better
<wpwrak>
tuxbrain_away: rafa had to go to the desert and he'll miss the nice barbecue we'll have at my place tomorrow. no surprise he's unhappy :)
<wpwrak>
tuxbrain_away: (tribute) yeah ! ;-)
<tuxbrain_away>
uff seems that finally we have found a good config of get rid of spam at drupal.... spammers (here are a lot of bad and ugly words that my daughter must not hear)
<wpwrak>
kyak: i'm not quite sure whether NAND or uSD is faster. by the bus width and bus type, NAND should win (8 vs. 4 bit, local bus vs. external bus). but then i've heard that uSD was faster. not sure how much overhead UBIFS adds.
<wpwrak>
rafa: (mp3/ogg recoding) how about a script that runs on the pc that uploads mp3s to the ben and recodes on the fly ?
<kyak>
aisa: there are a lot of packages not requiring patches, and during make only a notification is generated
<kyak>
i don't know why you decided so necessarily to get rid of it
<aisa>
kyak: the principle I was using was to remove noise to make revelvant lines easier to see.
<aisa>
this turned out to be a two or three bugs.
<aisa>
one was an error/warning for a condition that is normal.
<aisa>
two was the code being executed when it was not intended.
<aisa>
three is still not fixed, which is that the macro expansion is not protected from being expanded again by the shell.
<kyak>
not following you here..
<kyak>
bugs where?
<aisa>
I'm not sure what you were asking about either.
<aisa>
what does this: 'aisa: there are a lot of packages not requiring patches, and'
<aisa>
refer to?
<kyak>
are you Alan Post?
<aisa>
I am.
<kyak>
then i was referring to your "no warning when there is no patches directory" patch
<aisa>
ah, the "warning" in this case is an error message from 'ls'
<aisa>
not a warning that was intentional.
<aisa>
in fact, the code tried to not have the error be there.
<aisa>
but it was written in such a way that the feature did not work.
<kyak>
can you specify under which conditions you've seen such error message?
<aisa>
My choice of wording re: warning was to state that the code still worked.
<aisa>
make package/lojban-wordlists/clean package/lojban-wordlists/compile V=99
<aisa>
Namely, when a package has no ./patches directory.
<kyak>
then again
<kyak>
as i said above
<kyak>
there are a lot packages without patches directory
<kyak>
and i never seen an error message
<kyak>
why?
<aisa>
I can't speculate, you can look at the code and tell me ;-)
<aisa>
I'm not sure what you're driving at.  What are you intending for this conversation?
<aisa>
Can you tell me what you want?
<kyak>
just trying to understand
<kyak>
why you removed that warning
<aisa>
Have you looked at the patch?
<wpwrak>
kyak: the code is quite clearly inconsistent in itself. whether it's actually necessary to worry about the directory being absent is a different question :)
<aisa>
the original code did not work.
<aisa>
it wanted to test for the existence of the directory,
<kyak>
always worked for me
<aisa>
and then if it existed, run ls ./patches | wc -l
<aisa>
but,
<aisa>
no matter the first condition,
<aisa>
the ls was always run.
<aisa>
so the patch corrects this,
<aisa>
such that ls in only run if the first condition is true.
<aisa>
I promise this change works for you too.
<aisa>
and it works for me.
<wpwrak>
aisa: perhaps if there's a package that exhibits this, kyak can see for himself
<aisa>
I mentioned one earlier.
<aisa>
lojban-wordlists
<aisa>
the command:
<kyak>
if there is patches directory, with the patches inside, it applies them. If there is no such directory, there is a warning.. That's how it worked
<aisa>
make package/lojban-wordlists/clean package/lojban-wordlists/compile V=99
<aisa>
will demonstrate the error,
<aisa>
if you revert or don't update tracking_backfire
<aisa>
if you want the warning,
<aisa>
we should add it on purpose.
<aisa>
the warning was a side effect of bad code.
<kyak>
but it didn't throw an error or stop your build process?
<kyak>
because you said there was some error rather then warning
<aisa>
ok: ls had an error.
<wpwrak>
kyak: if you look at the code, you'll see that it explicitly tests for the directory. this would only serve a purpose if the objective was to avoid the error/warning. otherwise, just run ls and it'll produce empty output as well
<aisa>
the makefile neither cares, checks for, nor detects that ls had an error.
<aisa>
so the process continues.
<aisa>
kyak: I think this would all be much clearer if you looked at the code and we spoke about it.
<kyak>
ok, i got your point
<aisa>
rather than abstractly talking about what it may or may not be doing.
<kyak>
aisa: i see the code
<kyak>
it's ok :)
<aisa>
What about the code don't you understand?
<wpwrak>
aisa: that's a nasty question for this kind of rather subtle code ;-)
<aisa>
heh.  Indeed, I'm still working on one of the bugs, because there is a piece I don't understand.
<aisa>
What I'm really driving at, however,
<aisa>
is if we all understand the code,
<aisa>
I need to know what the code isn't doing that we would like it to.
<wpwrak>
aisa: i think your interpretation (that leads to the fix of avoiding the error) is plausible. another possibility would be that someone wanted the error (as a warning) but didn't trust the ls ... wc -l to yield zero in this case. occam's razor favours the former interpretation :)
<aisa>
ha!  Indeed, I'd much rather see a warning generated by make.  Though I'd rather see no warning at all because the condition is normal.
<wpwrak>
aisa: yes. don't warn if it's a quiet, normal day. no need for a Homeland Security Advisory System that's always at yellow :)
<wpwrak>
like someone wrote, "yellow is the new green" :)
<aisa>
kyak: I'm sorry I'm so grumpy, I am working on too many things at once today :-(
<kyak>
aisa: no problem, i just misunderstood you
<aisa>
Next time I'm confusing I'll endeavor to not be impatient about it, too.
<kyak>
and next time i'm drunk i'll not show up on IRC (i always say that) :)
<aisa>
LOL
<aisa>
what is your name?  Either your wiki username or commit name?
<kyak>
it's kyak
<aisa>
oh looksie, it only took me needing to look at the list.
<kyak>
yeah, the same name in the list
<aisa>
is it pronounced ki-yahk, kuyook, or exactly like it is spelled?
<kyak>
ehm, it used to be a random and unique combination of letters, no intended for reading out load :) but i guess it's the same as kayak, the boat
<aisa>
(I'm walking away again for a bit, I'll be around variably.
<aisa>
I think that is the current version, missing the wc -l.
<wolfspraul>
I think that was Werner's last idea
<wolfspraul>
it's all fine now, we don't need to waste time over every last quote :-)
<wpwrak>
my last idea is a use i also only spotted today. shell programming is full of surprises ;-)
<wpwrak>
wolfspraul: btw, two quick PR ideas: 1) next 1000 units, with the new stuff that's getting bundled. it's low-profile, but someone may pick it up.
<wpwrak>
wolfspraul: 2) when jlime is ready for inclusion, plus dual-boot is there as well, then you can start shipping bens with both options. (well, after passing a zen moment of reflashing :) that'll also be a newsworthy moment.
<wpwrak>
(that is, ben shipping with jlime dual-boot. not necessarily your reflash session ;-)
<wolfspraul>
yes I agree but this is all a lot of work
<wolfspraul>
I think I will focus on the Milkymist launch at 27C3 next
<wpwrak>
worthwhile work, i'd hope :)
<wpwrak>
why not try to make something out of the 2nd 1kunits ? see how it goes
<wpwrak>
you may find things that help with the mm launch as well
<wolfspraul>
I've started to write down random thoughts on the milkymist release
<wolfspraul>
haven't even talked with Sebastien yet, nothing can go in there that he doesn't agree with
<wolfspraul>
it takes time to craft a strong message
<wolfspraul>
I have started to contact Lattice about a quote, I think that would be nice
<wolfspraul>
but I need to ask 5-10 people for a quote, it always depends on whom you talk to, whether they 'get it', see mutual benefit, etc. etc.
<wpwrak>
well, you still have a bit of time for that. so that;s probably safe
<wolfspraul>
2 months
<wolfspraul>
not much
<wolfspraul>
getting a quote is hard work :-)
<wolfspraul>
there is a PR department on the other side
<wolfspraul>
I remember one time it took 6 months, of constant back and forth, to get a quote from Sony-Ericsson for a press release
<wpwrak>
they'll also want to find out who you are. they wouldn't want to support the local taliban-nazi-pedophile club, for example ;-)
<wolfspraul>
so we see
<wolfspraul>
but I appreciate your comment
<wolfspraul>
yes, if we had a better/more efficient news machine, a press release about the first 1k being sold, and the second 1k being manufactured is not bad
<wolfspraul>
there is bigger crap that gets broadcast
<wolfspraul>
and another one about Jlime/OpenWrt dual-booting is also not bad
<wpwrak>
not sure if you even want to define a "target market"
<wolfspraul>
well it's full of question marks
<wolfspraul>
I haven't even sent my 1k manufacturing report email yet
<wolfspraul>
yet alone a fully crafted press release
<wolfspraul>
let alone
<wpwrak>
i'd say, if you think you can do one about the 2nd k without sacrificing anything more important, then do it
<wpwrak>
see, so it's still news ;-)
<wpwrak>
sometimes, procrastination works in your favour :)
<wolfspraul>
andres-calderon: hey there, good to see you here! :-)
<wolfspraul>
I heard 100mil (2.54mm) is more common than 2mm
<wolfspraul>
this connector is for what? expansion header?
<andres-calderon>
yes, GPIOs
<wolfspraul>
oh I see, 2 rows of 25
<andres-calderon>
2.54mm x 25 pos = 63.5mm
<wolfspraul>
maybe we should then include a cable that has that connector on one side, and individual wires coming out on the other side
<wolfspraul>
sure, I agree
<wolfspraul>
smaller = better, imo
<wolfspraul>
there are 1.25mm pitch connectors too, I think
<wolfspraul>
I don't know much about the pros or cons for the intended use case later, though
<wolfspraul>
my feeling is whether we have a 2mm or other connector, we should include a cable so that people can easily solder individual wires to whatever target they have
<andres-calderon>
We also use two 2.54mm connectors (instead of one of 2mm)
<wolfspraul>
and in that case (if we include a cable anyway), I would think it doesn't matter so much whether the connector on the board is easy to get, or not so easy to get
<wolfspraul>
as long as at least going forward the connector we chose is not becoming obsolete
<wolfspraul>
that would be bad
<wolfspraul>
too bad that wpwrak is out right now...
<wolfspraul>
andres-calderon: if you are out later, I am sure wpwrak will have some feedback on this, you can check the irclogs at http://en.qi-hardware.com/irclogs