<kristianpaul>
but indeed that could drop prices and move ingenic soc to more general porpuses setups
<kristianpaul>
xburstduino ;) like board, why not? :-D
<wpwrak>
kristianpaul: if they're using the 4725B, i wonder why they didn't throw out the NAND too. the 4725 has two MMC controllers and can boot from MMC
<wpwrak>
NAND and MMC0 share pins. so if you choose NAND, you lose the 4 bit MMC controller
<kristianpaul>
my sie have 4725, and so far i remennber MMC is 1 bit
<kristianpaul>
but yeah, dropping nand will be could
<kristianpaul>
more gpio
<wpwrak>
the black PCB seems to be an older version. the yellow one is the latest, says rafa
<kristianpaul>
one more chip you can buy everywhere
<kristianpaul>
yup
<kristianpaul>
i was confused then :-)
<wpwrak>
(SIE MMC 1 bit) yes, of you have NAND. then you can only use the MMC1 controller, which is 1 bit. see, NAND costs you more than you may think ;-)
<kristianpaul>
indeed
<LunaFrizzle>
wpwrak, gotta go to bed now, I'll stick with the ben + ubb for now :)
<wpwrak>
no NAND would also make the layout a lot simpler
<LunaFrizzle>
wpwrak, thank you so much for all theses info, see ya
<kristianpaul>
and smaller
<wpwrak>
and if you choose to boot from USB, you could use the MMC0 controller for other things
<kristianpaul>
xburst have internal sram?
<wpwrak>
they should have a little, for booting
<kristianpaul>
some kbytes?
<wpwrak>
something 4 k-ish would be common. i'm too lazy to look it up :)
<kristianpaul>
np
<kristianpaul>
On-chip boot ROM 8KB
<wpwrak>
4 kB ROM and 8 kB RAM, according to section 3.5.2 of Jz4725B_pm
<kristianpaul>
4kB Boot ROM memory
<kristianpaul>
yeah
<kristianpaul>
well, having some tiny code running at 336Mhz still intersting :-)
<wpwrak>
oh, that's just for the first stage. then you load whatever else you want.
<kristianpaul>
hum? i dont understand
<kristianpaul>
i mean what whatever else i can load? (considering i was thinking in remove SDRAM chip :-) )
<wpwrak>
no, remove NAND. not SDRAM :)
<kristianpaul>
i want rip all ! ;)
<wpwrak>
kristianpaul: consider just power, headers, a few buttons, and a piece of paper telling you which buttons to press when ;-)
<DocScrutinizer>
"we" actually could give FR PCB to community now
<DocScrutinizer>
of course free binary, for windows ;-D
<wpwrak>
with the calypso ? hardly ...
<DocScrutinizer>
blah
<DocScrutinizer>
WTF is calypso??
<DocScrutinizer>
nm, Sean will not care anymore
<DocScrutinizer>
and I'm still hesitant to "break the rules"
<DocScrutinizer>
I always like to push as hard as I can, for community, but I'm not the one to ignore the limits
<DocScrutinizer>
as long as it's about (ex-)contractors
<DocScrutinizer>
I don't give a fkying F* about calypso though
<DocScrutinizer>
hell this component isn't even sourceable since almost 3 years
<wpwrak>
it probably still is. dunno if from ti, though
<DocScrutinizer>
plus if the PCB design were of Intel, I'l like to sue them still today, for #1024
<DocScrutinizer>
so what's Int'l's royalties in PCB design anyway??
<DocScrutinizer>
the size of their chip? or what?
<DocScrutinizer>
or did OM agree on never mentioning we are using this chip? ;-P
<DocScrutinizer>
nah, forget calypso, forget Intel. It's all about OM and Sean
<DocScrutinizer>
I always said there's pretty limited use in community getting full access to eachof the 8 layers of the PCB, but Wolf been always keen to disclose *all*
<DocScrutinizer>
I'm not really averse
<DocScrutinizer>
and now that we *can* do it, I even like to push an itsy bit
<wpwrak>
with gta02-core not getting components from sean and openmoko having abandoned technology anyway, the layout has pretty much drifted into irrelevance
<DocScrutinizer>
indeed
<DocScrutinizer>
that's why I think asking Sean about it is a lost case
<DocScrutinizer>
maybe he even doesn't own the technical stuff of FR anymore
<DocScrutinizer>
wonders idly how Wikireader ended at MEDION
<DocScrutinizer>
makes me rethink my previous statements and my usual practice of checking carefully the destination of sftp transfers ;-)
<DocScrutinizer>
but nah, I want to stay in business
<DocScrutinizer>
wpwrak: could you asl wolf about it, just what's his take on it all
<tuxbrain_away>
wpwrak: when do you think we can have a wpan0 interface on NN? you know use it as easy as we use usb0 now?
<tuxbrain_away>
wpwrak: did you read my first measures?
<tuxbrain_away>
250k 12m
<tuxbrain_away>
500k 12m
<tuxbrain_away>
1MÂ Â Â Â 11m if orientation is correct
<tuxbrain_away>
2MÂ Â Â Â 7m if orientation is correct
<tuxbrain_away>
this was for an atusb/atben pair I'm also courious about atben/atben and atusb/atusb
<tuxbrain_away>
not willing to flood but ,  wolfspraul have you see the first range results on fab atben/atusb?
<tuxbrain_away>
well time to some spanish revolution and then to flash/test some wpan, I'm really happy with the results :) my heartbeats had go lower when I see the test past
<wpwrak>
tuxbrain_away: hehe ;-)
<wpwrak>
tuxbrain_away: (wpan0) dunno. first, lemme test a few more things about the firmware. to make a version you can flash in all those devices.
<wpwrak>
tuxbrain_away: 6lowpan will be harder to use, because you may also have to introduce ipv6 to your network.
<wpwrak>
tuxbrain_away: (ranges) have you tried how far you can get with optimal orientation at 250 kbps ?
<wolfspraul>
no I haven't seen results yet, nothing conclusive at least
<wpwrak>
wolfspraul: he got 12 m indoors at 250 kbps and still 7 m at 2 Mbps (if holding the ben at the right angle). that's a bit better than what i obtained with my prototypes. (about 7 m here at 250 kbps with the right angle)
<wpwrak>
wolfspraul: so this looks pretty good. seems that the open-loop manufacturing worked ;-)
<wolfspraul>
that's for both 8:10 and usb versions?
<wolfspraul>
I read something about trouble with usb, clock stability or what it was (I didn't try to follow the entire conversation)
<wolfspraul>
everything works, everything can be sold? 100% yield rate?
<wpwrak>
that's between atben amd atusb for now
<wpwrak>
the clock stability was a problem of tuxbrain's laptop (some arm notebook) having very noisy timing. with a better machine, the results are stable.
<wpwrak>
(yield) i think he only tested one board from each set yet. so we'll see how that goes. but it means that the yield is > 0%, which was my greatest worry :)
<wpwrak>
(e.g., chip rotated the wrong way. bzzzt, game over)
<wolfspraul>
well, Tuxbrain needs to understand he is the manufacturer here. He can only sell features (and boards) that he has tested.
<wolfspraul>
I hope he understands that :-)
<wolfspraul>
every feature has to be tested on every board
<wpwrak>
i think he does. no worry there
<wpwrak>
what went wrong was that the smt fab went ahead without anyone testing what came off the line. that was high-risk.
<wolfspraul>
sure but that's what they will do if there is nobody to stop them
<wolfspraul>
the margins are too thin there (by design) to afford any sort of doubts or questions...
<wpwrak>
testing is just a matter of putting things in the right (physical) configuration and then "make usb" or "make ben". there are 1-2 operator inputs but that's all. have you seen this ? http://downloads.qi-hardware.com/people/werner/wpan/prod/
<wpwrak>
not sure if it was an attempt to push the margins or if their customers are just generally the trusting kind
<wpwrak>
from the way they work, i have the impression their typical customer doesn't worry very much about production issues. if the EDA system says it's okay, send the files to the fab and they'll take care of everything, right ? ;-)
<wpwrak>
so there's a bit of consulting work in their price. considering that this was a run with a never-before fabbed design, several unproven tools, and probably also tuxbrain's first, probably a reasonable approach. now we can go to the chinese penny-pinchers for the next million boards ;-)
<wolfspraul>
yes many people produce blind, but that's why you have so much crappy hardware nowadays, stuff you take out of the box that just doesn't work
<wolfspraul>
or some features don't work
<wolfspraul>
that's because you are the first one to run them on that particular device :-)
<wpwrak>
okay, that's even worse
<wolfspraul>
even for a brand company, it may be cheaper to catch those things at the retail end, with a no-questions-asked return/replace program
<wolfspraul>
you need this anyway for things that broke after testing
<wolfspraul>
so you can throw manufacturing issues into that program as well, if it's cheaper :-)
<wpwrak>
sigh. welcome to the fight club ...
<wolfspraul>
I'm all easy about this. If I order boards from tuxbrain and they don't work, I expect him to replace/fix my boards :-)
<wolfspraul>
but anyway, results of testing the first 2 boards seem good, and that's great!
<wolfspraul>
he made 100 each? or more?
<wpwrak>
yeah, and both waste a multiple of the value of the merchandise in logistical overhead and shipping ...
<wpwrak>
i think ~130 atben. not sure how many atusb.
<wolfspraul>
yes, but the margins are quite fat there
<wolfspraul>
ok
<wpwrak>
he also has a ton of pcbs left (making 100 costs almost at much as making 500, so he got ~500 of each). so if there's good demand, he can quickly make more. and actually begin having a margin :)
<wpwrak>
it's fun to watch the crystal drift with temperature changes ;-)
<dvdk>
starts to hate cmake. people complain about autofail tools? it can get much worse than that
<wpwrak>
meanwhile, in a parallel universe, the eclipse foundation publishes a document titled "The Open Source Developer Report"
<wpwrak>
dvdk: we're doing open source, so i think we should switch ;-)
<larsc>
uses MS Visual Studio C++ as an IDE for all his linux kernel work ;)
<dvdk>
wpwrak: well when porting other people's software (cmake is used by plplot), there's just not much we can do to move them over to visual studio :)
<wpwrak>
larsc: ah, i though you were doing it in C# with .net and do some automated conversion to C ;-)
<wpwrak>
dvdk: for me, make is one of these IT honeypots. just like TCP. people who don't understand the problem is solves try to construct "better" replacements that solve a subset. that's a fairly common pattern. what makes "make" and TCP special is they're the target of particularly persistent yet unsuccessful attempts at replacing them.
<wpwrak>
of course, the "i can do a better tcp" fallacy is great entertainment in research. when you get a paper with such a project, it's time to prepare the pop corn while watching the drama unfold ;-)
<wpwrak>
of course, what's even better is if a reviewer doesn't notice the handful of cases where the author actually knew what he was doing. e.g., van jacobson (kinda "Mr. TCP") once got a paper rejected with the reviewer claiming that the (anonymized for the review) author didn't understand tcp ;-)
<larsc>
yea, anonymized reviews can be amusing at times
<dvdk>
wpwrak: just getting back.  your IT honeypot thought really makes me smile.  c
<tuxbrain_away>
wolfspraul: yes I will test all the board, all boards shiped will pass the werner test and a distance test, if there is faulty ones I will agree with werner how to analize. there was 135 atbens 110 atusb, I hope I will test enough(and that they pass the test) over the weekend to start selling on tuesday (monday is hollidays here)
<wolfspraul>
nice
<tuxbrain_away>
btw how many do you want? :)
<wolfspraul>
then we need to make sure the software works as much as possible out of the box in the OpenWrt image (that's what I will go after)
<wolfspraul>
how are you selling them? pair of ben+usb?
<wolfspraul>
let me see the price and all when it's online :-)
<wolfspraul>
I first need 2 or 3 pairs I guess, then I need to think whether I can bundle it somehow, or sell, but that will require more testing and thinking.
<tuxbrain_away>
wolfspraul: totally agree, I don't know if with the dirtpan we can do a wpan0 interface that will be the best of the best case!
<wolfspraul>
also I don't want to give any away because that would devalue the product on your end - don't want to do it
<wolfspraul>
we give away stuff of other companies :-)
<tuxbrain_away>
whatever I will send some to some devels
<wolfspraul>
maybe we can make some games where people can play with multiple Bens
<tuxbrain_away>
ok I must leave
<wolfspraul>
l8
<wpwrak>
wolfspraul: (games) you could to the "snake in a tunnel" thing ;-))
<wpwrak>
s/to/do/
<Fusin>
hi qiots
<DocScrutinizer>
hi
<Fusin>
hi doc
<DocScrutinizer>
wpwrak: you're aware a *proper* QA still is a bit more challenging than a mere sw-based test of functional aspects. Of course you know. I'm just pondering idly where's the point where this kind of open hw manufacturing has to start to think about such things like voltage / temperature stress tests. Given the fact we mostly got away without any such proper QA at OM ;-P
<wpwrak>
DocScrutinizer: i would put most of this into the domain of "design verification". unless you actually see a lot of failures in the field due to parts not meeting specs, there seems little point in testing all this, too
<DocScrutinizer>
some stories for the general background: on really large scale production, you probably go to stress a 5000 sample, then if you e.g find 1% drops out at temperatures <5°C you try to find *other* parameters of the DUT that indicate same problem - like "oscillator takes >3*Tavrg to start" and then you test for these parameters instead
<wpwrak>
DocScrutinizer: i mean, we're not designing nuclear reactors here. well, considering it, that may not be a good example :)
<DocScrutinizer>
a simple VDD variation stress test is rather standard though, as it tells you a mad friggin lot about real state of DUT
<wpwrak>
DocScrutinizer: yup, exactly. you need to observe some actual failures. our sample size is way too small for that. maybe we'll discover one or two systematic defects from this run, maybe with the opportunity to do better the next time, but with such tiny quantities, something has to go massively wrong before you even get a blip on the radar.
<DocScrutinizer>
Iknow
<wpwrak>
DocScrutinizer: (vdd) that needs equipment ... tuxbrain can't even afford a low-end scope. so ...
<DocScrutinizer>
Iknow
<DocScrutinizer>
just thinking
<Fusin>
Iknow you know :D
<Fusin>
lol
<wpwrak>
Fusin: iKnow - quick, before apple grab it ! ;-)
<DocScrutinizer>
you know I always like to have a complete plan, so you know what you are discarding / postponing, and why
<wpwrak>
DocScrutinizer: my tests try to test everything i can do with on-board means and with a pair of devices. the chips also detect voltage excursions and such, so there's a chance to pick up some of these. also, if there's massive droop, it'll show up in the transmit test.
<DocScrutinizer>
better go "that's the optimum right way: A, B, C... - and this is what we do right now: B as we can't do A and C is nonsense"
<Fusin>
lol @ wpwrak
<DocScrutinizer>
I'm well aware this device isn't properly ESD tested and whatnot
<wpwrak>
DocScrutinizer: we what can slip through the tests are parasitic effects and slight performance degradations. e.g., you may only get half the range. but you'll probably never know if this is because of a poorly performing device or because of your environment.
<Fusin>
what about an iBen?? :-> and iNano, iOpenMoko?
<Fusin>
food time
<Fusin>
bbl
<wpwrak>
DocScrutinizer: atusb has TVS at least ! ;-)
<DocScrutinizer>
tranzorbs?
<wpwrak>
varistors
<DocScrutinizer>
aah
<wpwrak>
digi-key 445-2559-1-ND
<DocScrutinizer>
nah
<DocScrutinizer>
too lazy
<DocScrutinizer>
will be fine
<DocScrutinizer>
good job!
<wpwrak>
yeah. they're designed for such things. ought to work :)
<DocScrutinizer>
also on antenna? ;-P
<wpwrak>
the antenna is supposed to be isolated
<DocScrutinizer>
indeed, I think tehre's a balun or sth iirc
<wpwrak>
otherwise, you'll eventually etch it away just with your hands :)
<wpwrak>
there's a balun, yes
<DocScrutinizer>
good enough for ESD-prot
<wpwrak>
kewl. one worry less :)
<DocScrutinizer>
hehe
<wpwrak>
the boards are designed such that you should be able to solder an antenna connector (U.FL type), so it's nice if this doesn't cause an esd hazard
<DocScrutinizer>
oh, yu gotta remove a 0R then?
<wpwrak>
(antenna connector) with a bit of scraping and it's pretty much irreversible. but can't hurt to have that option.
<DocScrutinizer>
aah
<DocScrutinizer>
yes, good job again
<wpwrak>
thanks :) your praise honors me ;-)
<DocScrutinizer>
sorry, my straight honest notion about it, nothing implied
<wpwrak>
heh :) still good to know that my hack passes scrutiny
<DocScrutinizer>
just listening to my inner "Ahh varistors :-) AAAHH an option for connector :-))"
<DocScrutinizer>
another such detail and I'm sold to the device, no matter if I need it or not :-)
<DocScrutinizer>
what's the TX power? Your bandwidth figures seem pretty decent
<wpwrak>
hmm, does dfu-upgradeable firmware count as a "nice" feature ?
<wpwrak>
+3 dBm = 2 mW
<DocScrutinizer>
I think is counts, yes
<DocScrutinizer>
(2mW) :nod: would consider that a design well in bound of expectations
<wpwrak>
(take that, whitequark, with your 1 W ghettoblaster !)
<DocScrutinizer>
now for next version of device which comes with 4GB flash mass storage integrated ;-)
<wpwrak>
(2 mW) that's the nominal tx power. i don't have the means to measure the really emitted power. it seems that there's nothing significant at the 1st harmonic. then the range of my equipment ends, too.
<DocScrutinizer>
10m range for 2mW is nothing to worry about anyway, pretty ok
<DocScrutinizer>
though with a proper antenna and good RX you should reach 100m easily
<DocScrutinizer>
where proper==external here
<wpwrak>
yeha, i think it's also a range for real-life use. particularly when i compare it with wlan.
<DocScrutinizer>
indeed
<wpwrak>
some chip makers claim that sort of distance, yes
<DocScrutinizer>
nah, after my records got stolen 3 times in my life, I feel not any bad with it anymore
<wpwrak>
DocScrutinizer: 3 times ? maybe you should consider more upscale neighbourhoods ;-)
<DocScrutinizer>
makes a total of like 4000 stolen vinyl and CD, some 300 of them bootlegs
<wpwrak>
in backups we trust :)
<tuxbrain-mob>
testing the irc on the mobile, seems that all works ok :)
<DocScrutinizer>
gor pissed on music somewhat, even since the 2nd time
<wpwrak>
but yes, i had some CDs stolen from my car once, too. naturally, most of them not yet backed up :-(
<DocScrutinizer>
now rethinking my life w/o music
<wpwrak>
tuxbrain-mob: ben + dirtpan ? :)
<DocScrutinizer>
alas a lot of the 80's stuff never will come back
<DocScrutinizer>
e.g B-52s
<DocScrutinizer>
hard or impossible to get all albums, even for gold
<DocScrutinizer>
so FSCKYOU sony, EMI, whatever the name
<tuxbrain-mob>
hehehehe create the wpan interface and then we can talk about it
<wpwrak>
DocScrutinizer: let's call it the distributed global cultural conservation project ;-)
<tuxbrain-mob>
I will recoonect later see you
<wpwrak>
tuxbrain-mob: with dirtpan, you have IPv4. so ...
<DocScrutinizer>
indeed, and you're free to laugh at me but I considered to start an "official" such project
<wpwrak>
tuxbrain-mob: no support for atusb yet, though. so you need one ben as gateway.
<DocScrutinizer>
modulo the "distributed"
<DocScrutinizer>
just for music
<DocScrutinizer>
as it's so goddamn volatile you'd never expect in times of ubiquitous copy technology
<DocScrutinizer>
just the general notion of "ther's for sure a copy out there" makes good music vanish into oblivion it seems
<DocScrutinizer>
there *IS NO* mastertape!
<DocScrutinizer>
anymore
<wpwrak>
DocScrutinizer: (project) good luck ! :) i think you need a few paradigms shifts to happen before such a thing can fly, but it'll probably take a few martyrs to get there.
<DocScrutinizer>
nah, write-only petabyte store in a bunker would be a simple easy approach
<wpwrak>
now ... there's that critically important interrupt. if it leave it on, it fires all the time (which is expected in that case), wasting system resources.
<wpwrak>
if i turn it off completely, the thing just works. this makes no sense :-(
<DocScrutinizer>
everybody (incl all artists) could get a nuke-safe backup of their artwork, given they agree everybody can "watch" the backup after tedious filling of papers etc
<DocScrutinizer>
the duty of the archive managers (and tools) would be to assure the readability of content over the decades, and keep doublettes out, and process read-inquiries
<DocScrutinizer>
plus of course manage world-readable state after expiry of (C)
<DocScrutinizer>
whenever that is
<DocScrutinizer>
such an archive also would be a nice way to claim (c) by mere timestamp and signature of the artwork
<wpwrak>
you'll never get this past the labels. they'll just claim that they keep the backups. their milk cows are probably already forbidden by contract to let anyone outside maintain a backup.
<DocScrutinizer>
the archive won't care :-)
<wpwrak>
nice. if i make the transfer large enough, the interrupt starts to matter. the world makes sense again ;-)
<DocScrutinizer>
existence of backups isn't covered by any (c)
<DocScrutinizer>
just distribution is
<DocScrutinizer>
the global art archive isn't world readable in a simple way, so any sharing concerns are moot
<wpwrak>
(c) covers copying. you can fight it out with their lawyers whether external but non-public backups constitute fair use. and if your backups go public within the 70 or whatever years, the case is pretty clear.
<DocScrutinizer>
think of it like the US congress library
<wpwrak>
call it a vault. to be opened by your grand-grand-childen ;-)
<DocScrutinizer>
just for digital and digitized artwork
<wpwrak>
and good luck convincing anyone your business will still be around in 70 years. note that you either need to laser the data into gold or such, or make regular refresh copies.
<DocScrutinizer>
instead of printed books
<DocScrutinizer>
refresh copies is the duty of the employees there - you'll of course need sponsors, or a foundation
<wpwrak>
conventional digital media only lives for a few years, decades at best. your cd-r will be unreadable in 70 years, probably even if you add a lot of redundancy
<wpwrak>
yup
<DocScrutinizer>
also you might consider to ask for fees for reading their own backups, just in case. Maybe even fees for allowing them to access their own backups any time
<wpwrak>
well, you can probably offer a number of add-on services, yes :)
<DocScrutinizer>
this way it becomes kind of a mega-remote-backup facility
<wpwrak>
as long as Anonymous don't pay you a friendly visit, making a little download :)
<DocScrutinizer>
which you may use for relatively little fee, given you agree on the terms of semi-scientific public use
<wpwrak>
it would of course be safer if you really took the data offline until the public domain data.
<wpwrak>
s/data/date/
<DocScrutinizer>
I admit I haven't spent more than maybe 15min on that idea, just found it compelling when it occured to me
<wpwrak>
and you want to have a minimum "keep it closed" interval. otherwise, people will just use you as public web space, and send you their warez collection.
<wpwrak>
so, better to have the minimum near 70 years anyway. that way, even pirated content will be safe :)
<DocScrutinizer>
data offline was the idea, "others" can access only by paying insanely high fees or by going thru a real nasty paperwork that takes months
<DocScrutinizer>
or just go there to *listen*
<wpwrak>
if you let "others" access it, then you open yourself to the usual litigation
<wpwrak>
make it a vault. buried treasure. let generations to come marvel at your work.
<DocScrutinizer>
that's the basic idea
<wpwrak>
the problem is finding a way to ensure this kind of longevity.
<DocScrutinizer>
you nevertheless need candy to lure folks in
<DocScrutinizer>
the candy is a) they can access it themselves any time though for some fee maybe
<wpwrak>
then you have the authentication problem
<DocScrutinizer>
we're hackers! we don't have such problems, we got the solution to them
<wpwrak>
the candy would be the eternal fame. make good PR. it may work.
<DocScrutinizer>
b) for a really high fee forensics, scientists etc can search the *content*
<wpwrak>
you still have the issue tht labels will try to kill you on general principles. after all, the artists sell their right to the labels, so they have no right to let you have an archival copy, unless the label agrees. and why would they ?
<DocScrutinizer>
c) everybody can search the *directory*
<wpwrak>
that is, unless you get them to agree to your plan in the first place. so plan on some budget for travel, a few suits, and long meetings with IPR lawyers.
<DocScrutinizer>
nah, you sell the (C) but you're always the owner of your own artwork and may make copies for your own purpose as many as you like
<DocScrutinizer>
you just mustn't *COPY* (means "distribute")
<wpwrak>
you could sell it to the labels as a protection against laws constraining them. e.g., laws that weaken the protection for apparently abandoned works.
<DocScrutinizer>
e.g
<wpwrak>
read the laws. they talk about copies, not distribution.
<DocScrutinizer>
there's a lot of potential benefit in such a global un-nukable write-only/no-delete/no-general-world-access lib
<wpwrak>
sure. you just need to pull it off ;-)
<DocScrutinizer>
(c) isn't a problem of the GAA though, if labels want to sue somebody, they have to start at their artists who claim they are owners of that stuff when putting it into that archive
<wpwrak>
maybe talk to google. they love to collect data. and they can talk eye to eye with labels. unlike you, who starts with a legal budget handicap of a few megadollars.
<DocScrutinizer>
and depending on whether submitter makes description world-readable or not, labels never may get to know about it
<DocScrutinizer>
wpwrak: exactly, why didn't I think of google first instance
<wpwrak>
(sue the artist) good point. this means that the index shouldn't be public. otherwise, you're exposing your customers.
<DocScrutinizer>
"the eternal youtube"
<DocScrutinizer>
that's up to the customer to set their index entry public or not
<wpwrak>
well, that's choice, yes
<wpwrak>
s/choice/a choice/
<DocScrutinizer>
the only immutable precondition is they agree on never-erase policy and disclosure after $random time depending on what they declare the stuff to be
<DocScrutinizer>
max maybe 100 years which would cost them quite some money, 10 years and you go for free
<wpwrak>
hmm, you'll probably get lawsuits on erasure
<wpwrak>
10 years means that you'd be at risk of distributing pirated material
<DocScrutinizer>
we don't guarantee non-erasure, we just say there's no way for *user* to ever hit the delete button
<wpwrak>
well, they'll send their lawyers ;-)
<DocScrutinizer>
sure we get problems with pirated material. Given the never-really-fileshare concept we me get away with it nevertheless
<DocScrutinizer>
or extend the period by another 10 yeras on a simple dispute
<wpwrak>
pornstarlet X makes some movie at age 18. things it's work conserving and sends it to you. ten years later she finds god and wants all copies destroyed. including yours. maybe she has a rich husband by then who pays for her legal extravaganza.
<DocScrutinizer>
who's sending their lawyers to facebook to make sure their private data got erased? ;-P
<DocScrutinizer>
starlet -> extend non-disclosure to 100
<DocScrutinizer>
set index to hidden
<DocScrutinizer>
done
<DocScrutinizer>
can't erase sorry -our technology doesn't even allow that
<wpwrak>
scenario 2: same pornstar, but it's fan Y who sends you her movie, claiming he's got the rights. then she'd go after you too, and you wouldn't even have a usable contract holding you free from erasure requests in this case.
<wpwrak>
(facebook) oh, i'm sure they get such things
<DocScrutinizer>
and just in case we get a legal order to erase, we still can do. Rmind we never *guaranteed* never-erase
<DocScrutinizer>
though SOP for erase request is "set disclosure time up to max, set index and description to hidden"
<DocScrutinizer>
oh and "deny disclosure requests, unless they are by law enforcement"
<wpwrak>
yeah, you could do that. dunno what the legal situation would be. this may be something without precedent. can you be forced to destroy an illegal copy you vow to never touch before it enters the public domain ?
<DocScrutinizer>
prolly not
<DocScrutinizer>
as there's no way for foe lawyer to prove you even are in posession of that copy anymore
<wpwrak>
(law enforcement) sure. they'll just subpoena what they need. add it to the damages they sue you for.
<DocScrutinizer>
hey, that's a Schroedinger's cat :-D
<DocScrutinizer>
sorry I can't destroy that allegedly existing copy, as I promised I never will touch that tape, so nobody can know if there's that copy on it
<DocScrutinizer>
nobody can force me to touch that tape unless they got sound clue about their copy being on it
<wpwrak>
i don't think it works like that ;-)
<wpwrak>
"sorry, you can't search for my meth lab unless you can have proof it exists" ;-)
<DocScrutinizer>
maybe not in US - for sure in sme northern EU countries :-)
<DocScrutinizer>
only police may search for my meth lab, and even those need a judge's order to do so
<DocScrutinizer>
you can't sue the mayor for the morphine in their town's bunker
<DocScrutinizer>
though the mayor for sure isn't allowed to "own" morphine
<DocScrutinizer>
generally to get sued for posession of sth, you need to have *access* to it
<wpwrak>
you can start a lawsuit and ask the court to order a search. no problem.
<DocScrutinizer>
let's assume there'd be a technology that doesn't allow to unzip/untar the tapes prior to e.g 2100. Do you think anybody could ask for deletion of the tapes for the mere possibility there's some material on them?
<DocScrutinizer>
let's assume I got two chemicals that - when mixed - react to give meth after 50 years. Would this be illegal?
<DocScrutinizer>
even when I mix them, when could somebody reasonably start a lawsiut against me for it?
<DocScrutinizer>
in 1 year, in 25 years? immediately? what if I destroy the whole set after 49 years?
<wpwrak>
(meth) probably not
<wpwrak>
(copyright) who knows ?
<DocScrutinizer>
nah, each brick in my wall holds the encrypted latest (c) songs of $random_artist - I just had to find the right decryption method and I'd get sued for posessing the brick
<DocScrutinizer>
or could I only get sued for *processing* it?
<wpwrak>
in some places, you can even go to jail for not being able to provide the key ;-)
<DocScrutinizer>
I, I'm happy to share the key with $WORLD, it's simply "idiot!" - alas I have no clue about the *
<DocScrutinizer>
*process*
<wpwrak>
you'll discuss these fine philosophical points with your cellmates :)
<DocScrutinizer>
can I go home now? ;-D
<wpwrak>
and don't forget - never reach for the soap ! :)
<DocScrutinizer>
hehe
<bartbes>
DocScrutinizer: god forbid you carry a piece of paper into the us with on it the decimal representation of a cryptographic key used for drm!
<DocScrutinizer>
that's exactly what this GAA basically is about
<DocScrutinizer>
I know, I got a t-shirt. Will this work better? ;-P
<bartbes>
wpwrak: instead, claim that the soap contains a song
<larsc>
i have all my data encryted in /dev/zero with xor. just need the right key ;)
<DocScrutinizer>
larsc: \o/ :-P
<DocScrutinizer>
considers to make another t-shirt with larsc 's nice statement
<DocScrutinizer>
recalls the cop with t-shirt >>if you'd say "PLEASE SOMEBODY SHOOT THE PRESIDENT", I'd have to arrest you
<DocScrutinizer>
only existed in my fantasy
<DocScrutinizer>
or - very simple - get a firewall in front of GAA that doesn't allow access from any US location - done
<DocScrutinizer>
China and others are going mega-LAN rather than internet. The only problem with USA is they think they *own* the global internet
<DocScrutinizer>
hell, I bet some of them still think they own the globe
<DocScrutinizer>
while on the other hand their citizens not even own the hardware they paid for
<wpwrak>
there's a tendency of going "inside". e.g., also facebook works that way.
<DocScrutinizer>
>tear down all churches immediately - they serve for some rogue individual to pin papers with illegal ideas written on them t the doors<
<DocScrutinizer>
starts to wonder if he's going silly
<wpwrak>
i think you know that the powers that be had a rather keen interest in arresting luther. if not, wikipedia is your friend ;-)
<DocScrutinizer>
or maybe it's some politicians going utterly silly
<DocScrutinizer>
wpwrak: what do you think why I made up this silly example
<wpwrak>
good :)
<DocScrutinizer>
I don't recall having heard about a singe church or even church door getting problems due to that though
<DocScrutinizer>
nowadays the common sense is "sue the door, make it reject pins"
<wpwrak>
they probably took care of their internal undesirables discreetly back then
<DocScrutinizer>
ooh, they do today as well, on all levels. But they extended their PR to accuse the door to be a "Mit-Stoerer"
<DocScrutinizer>
as the door did nothing to avoid that paper oinned at it
<DocScrutinizer>
pinned*
<DocScrutinizer>
next step: accuse the sun for providing light needed to read the paper
<wpwrak>
yup. they've learned. the "sudden unexpected death after quick and severe illness" doesn't work so well anymore these days. but you can neutralize your enemies just the same. don't even have to leave the office :)
<DocScrutinizer>
yup
<DocScrutinizer>
finding somebody who "got raped" is a simple and rather inexpensive and effective way to neutralize enemies nowadays
<DocScrutinizer>
and there's just so much you can do against such weapons
<DocScrutinizer>
way smarter than Polonium ;-P
<wpwrak>
simple rule: never set foot into any fundamentalist abrahamic country
<DocScrutinizer>
yeah
<DocScrutinizer>
but what to do when the country where your foot is goes fundamental?
<wpwrak>
run :)
<larsc>
they'll shoot your before you reach the border
<DocScrutinizer>
that's what I always fail to get -what's the use in forcing to stay those who disagree?
<DocScrutinizer>
I'd see the pint in shooting those who stand up
<DocScrutinizer>
point*
<wpwrak>
keep those from leaving who would if it was easy. that particularly includes well-educated people who could easily find work abroad.
<wpwrak>
anyway ...
<qi-bot>
[commit] Werner Almesberger: atusb/fw: revert most of the user_setups change and use simple callback instead http://qi-hw.com/p/ben-wpan/bbe27fc
<qi-bot>
[commit] Werner Almesberger: atusb/fw/: moved common elements of DFU processing to dfu_common.c http://qi-hw.com/p/ben-wpan/2544004
<qi-bot>
[commit] Werner Almesberger: atusb/fw/usb/atu2.c: use implicit race-free "and" when writing to UDINT/UEINTX http://qi-hw.com/p/ben-wpan/f9681e5
<wpwrak>
DocScrutinizer: (most problems) naw, think of engineers and such. many people may hate the system yet have too much to lose for open rebellion (or sabotage, etc.)
<DocScrutinizer>
if those dudes/folks would act smart, it'd be even way more scary
<DocScrutinizer>
glares at USA
<DocScrutinizer>
also glares at Hungary
<DocScrutinizer>
bbl
<rjeffries>
is wpwrak awake?
<rjeffries>
looks like maybe he is
<rjeffries>
this idea will take a few lines. pls. bear with m.
<rjeffries>
Goal: be able to use mouse and external keyboard with Ben Nanonote.
<rjeffries>
Possible to leverage cleunt USB on Ben as follows:
<rjeffries>
a little board prolly AVR based that has Two USB Host ports. (moer on this later)
<rjeffries>
one USB host port attaches to Nanonote
<rjeffries>
the 2nd USB host port goes to a USB hub so it supports 1x USB mouse and 1x USB keyboard
<rjeffries>
there is software on Ben that "understands"Â Â a simple protocol that the external USBx2 board uses to
<rjeffries>
tell Ben it is plugged in, and that it has one or two USB devices typically a mouse and a keyboard
<rjeffries>
for keyboard, keystrokes come into the USB2x board, and are sent to the "driver" on  Ben
<rjeffries>
likewise for the mouse
<rjeffries>
THE END
<rjeffries>
yes, compared to a future Nanonote with USB host this is the long way home
<DocScrutinizer>
rjeffries: there are such contraptions, called USB-network or USB-sync-cable or whatever, usually used to link two windows desktop PCs via USB
<rjeffries>
wpwrak those would connect two usb hosts together, correct?
<DocScrutinizer>
I'd like to ponder if I might go thru "make USB hostmode work" part 2.5 :-)
<rjeffries>
what do you mean DocScrutinizer ??
<DocScrutinizer>
probably it's not completely out of sight to use Ben's USB B connector to simulate a USB A host
<DocScrutinizer>
given you use some additional gear, like a hub with upstream VBUS, or a Y-cable
<DocScrutinizer>
maybe some resistors
<rjeffries>
DocScrutinizer to my mind, there are two use cases, but are Human Interface Devices: mouse and keyboard
<DocScrutinizer>
rjeffries: believe me, there's a lot of usecases for USB hostmode you'd not even think about
<DocScrutinizer>
I was amazed what users are going to do with USB hostmode when I enabled it on N900 ;-)
<rjeffries>
little AVR computers are ridiculously cheap now. the PCB for this ultra tiny one is about $1 $SD. plus BOM and assembly
<rjeffries>
docScrutinizer remin me what SOC the N900 uses
<wpwrak>
shall return after feeding
<DocScrutinizer>
rjeffries: yes, but why going this tedious awkward path of a micro-host with all the non-standard drivers etc pp, when you can mod the USB on NN to play host role?
<DocScrutinizer>
rjeffries: OMAP3430, but that's mostly irellevant for USB hostmode (modulo the fact the OMAP3430 MUSB core made by mentorgraphics was a real bitch to convince to do hostmode)
<DocScrutinizer>
on NN I guess USB is via bitbang or a way simpler USB hw interface inside SOC, so it's even simpler to implement hostmode there than it was for OMAP
<DocScrutinizer>
general rule: the difference between USB gadget and USB host are 2 resistors, a 5V line, and another driver in software
<DocScrutinizer>
on the PHY protocol level, there's almost no difference between a host and a gadget, means the data lines remain the same and no hw patches needed
<DocScrutinizer>
think of it like ethernet, where the host does also PoE
<DocScrutinizer>
there's no real difference between your NIC in PC and the webcam you attach via ethernet
<DocScrutinizer>
except for the host may provide Power over Ethernet (which you can fake, like you'd do for USB hostmode), and with USB you also got different plugs on each end, which you can deal with by using an adapter
<DocScrutinizer>
see the posts about Y-cable and USB on openmoko(-kernel?) ML and wiki, and also on talk.maemo.org (http://talk.maemo.org/showthread.php?t=65232 and previous lengthy threads)
<whitequark>
DocScrutinizer: duh? is the USB hostmode really so easy?
<DocScrutinizer>
:-D
<DocScrutinizer>
what can I say?
<rjeffries>
DocScrutinizer I have ZERO desire to add an external MCU. Ben useability would improve a LOT by having external keyboard and mouse, and doing that your way would be Most Excellent
<rjeffries>
whitequark: USB Host mode allows external (good) keyboard and a mpuse
<whitequark>
rjeffries: I know what USB host may be used for :)
<whitequark>
but I've heard a lot of times that it is quite resource consuming to implement it correctly
<rjeffries>
do you question how valuable a more useable keybaord is?
<whitequark>
rjeffries: not at all. I do question whether an USB host done entirely in software is possible at all
<whitequark>
if it (somehow) is, then it would be incredibly good, as the device I'm working with also misses a hardware host and it is much worse without it
<DocScrutinizer>
so if there's really interest in supporting this, I'm willing to give it a try and have a look at schematics and drivers. The sw bits need to be done by somebody else though, I can only give advice what to do and what to "mod" on hw side (cable with 2 resistors or whatever we may need)
<kristianpaul>
moment, what will happen with usb-boot with that hw mode?
<kristianpaul>
s/mode/mod
<DocScrutinizer>
the resources needed on sw side are not much different for host and gadget
<whitequark>
DocScrutinizer: do you know any working examples of bitbanging host on any MCU?
<DocScrutinizer>
kristianpaul: what should happen when there's a modded cable in your drawer? ;-)
<kristianpaul>
oh boy :-)
<DocScrutinizer>
I'd guess there are zillion of examples of bitbanged hostmode on MCU out there in the internets
<DocScrutinizer>
I bet wrt has such drivers, as there are plenty of routers that allow plugging in a USB stick for mass storage file server functionality
<DocScrutinizer>
on all those fritzbox and whatnot DSL-LAN-WLAN-roters
<DocScrutinizer>
routers*
<larsc>
but all of these have hw host mode
<DocScrutinizer>
haha
<whitequark>
yeah, most of them have EHCI
<DocScrutinizer>
what's hw hostmode, after all?
<larsc>
well, not sw
<larsc>
;)
<kristianpaul>
just a tranceiver i guess
<DocScrutinizer>
well, for sure they don't all have a MUSB-HDRC core on their SOC
<whitequark>
DocScrutinizer: I always thought it's just several FIFO's, an NRZI encoder and a state machine for packet handling, right?
<whitequark>
all these things are quite costly when implemented purely in software
<DocScrutinizer>
right
<whitequark>
and via bitbanging
<DocScrutinizer>
well, whatever they are implemented - they are IDENTICAL for host and gadget
<larsc>
you might do this via an coprocessor but certainly not on the main cpu
<DocScrutinizer>
you'te alrready doing it on Ben, whateve way
<DocScrutinizer>
the USB data transmission is symmetrical bidir
<DocScrutinizer>
host/gadget is decided on a way higher usually sw level
<whitequark>
DocScrutinizer: I've found just 1 (one) bitbanging implementation. it uses four Parallax Propeller chip cores overclocked to 96MHz and working simultaneously. I don't really think that Ben's cpu can handle this load
<DocScrutinizer>
so it doesn't matter if Ben is doing bitbanging, or has hw FIFOs or whatver, we'll simply re-use them
<larsc>
whitequark: there is a usb stack for avrs
<larsc>
DocScrutinizer: no
<whitequark>
larsc: V-USB? it's device-only
<DocScrutinizer>
uhuh
<larsc>
it's not that easy
<DocScrutinizer>
why?
<larsc>
whitequark: ah ok
<whitequark>
larsc: I meant "just one host implementation"
<larsc>
DocScrutinizer: because you can't turn the usb gadget ip core into an usb host ip core
<DocScrutinizer>
for all I know there's ot that much difference in PHY and 2nd layer, between host and gadget
<whitequark>
DocScrutinizer: ahem. if it's that simple, then why no one has implemented this? an ability of using hw usb gadget as hw usb host is definitely a killer feature. but can you point me to any Linux implementation of host-via-gadget?
<DocScrutinizer>
tzzz, so you got another friggin IP core there?
<DocScrutinizer>
whitequark: I'n not arguing on such level. I offered to look into schematics, datasheets, and whatnot. If you like to give up on a "hasn't been done yet" assumption, OK. I'm out
<whitequark>
DocScrutinizer: okay, dump that message. I'll get a better explanation then
<DocScrutinizer>
I made hostmode for N900 work, though *Nokia* told 100 times "It can not work, will never work"
<larsc>
but the ip core actually supports host mode
<larsc>
the jz4740 gadget ip core supports only device mode
<DocScrutinizer>
I feel this discussion is a bit discouraging, and I have no interests in Ben (not even own one), so you're free to implement the micro-host adapter approach, it's known to work
<DocScrutinizer>
o/
<DocScrutinizer>
btw oops, the connect-2-PCs adapter obviously is the othr way round, you'll need the "male" variant when that adapter is "female"
<wpwrak>
hmm, not sure if some facts would be appropriate for this discussion ... :)
<DocScrutinizer>
whatever, I wonder what makes you think the MCU on such an adapter is better siuted to do the hostmode job than Ben's SOC
<DocScrutinizer>
clears a topic on his todo list
<whitequark>
wpwrak: may we hear them?
<wpwrak>
1) almost everyone who implement usb host or device uses hardware support (NRZ, bit-stuffing, CRC, usually up to and including automatic ack, flow control, EP demultiplexing, etc.)
<wpwrak>
2) the one exception i know of is v-usb, which provides a low-speed device.
<wpwrak>
3) it's correct that at the PHY, device and host are very similar.
<wpwrak>
4) at the higher protocol layers, they differ. you still see that they're related, but USB is an symmetric protocol, so their roles are not easily reversed. e.g., any transfer is always initiated by the host. a device that has data to send waits until the host asks for it.
<wpwrak>
5) the jz4720 has a host controller and a device controller. unfortunately, they use separate pins, and the pins of the host controller are hidden under that black epoxy or whatever splotch.
<wpwrak>
6) i see no reason why you couldn't implement usb host in the v-usb way, i.e., via GPIOs. you may violate the standard by not getting all the timings right, but only few devices may notice that.
<wpwrak>
7) whether you can use the D+/D- lines of an existing USB device implementation depends on whether you can disable the pull-up and on whether you can properly bit-bang them (patterns and speed)
<whitequark>
wpwrak: hm. you only need 1.5MHz to plug in a HID device. that's probably less than atben requires
<whitequark>
but on 4725B (and 4740 has the same USB gadget), USB core has dedicated pins, which are not connected to any GPIOs, so you'll have to use other pins anyway in GPIO scenario
<wpwrak>
some USB controllers have the option of treating D+/D- more or less like GPIOs (for testing). but i'm not sure the 4720/etc. is among them. so far, it doesn't look good
<whitequark>
wpwrak: can you remind me, how long it takes for jz47xx core to set a gpio?
<wpwrak>
the "speed of light" is about 12 MHz
<wpwrak>
(read the description of the device controller) doesn't look good. there are test modes but they don't do what you need. you're better off just bit-banging GPIOs.
<whitequark>
so 1.5MHz should be more than doable within software
<wpwrak>
DocScrutinizer: so, get ben+ubb and hack away ! ;-)
<wpwrak>
whitequark: yes
<wpwrak>
whitequark: compared to the AVRs, you also have the advantage that your core runs a lot faster. so you have more time for bit-level things like NRZ and CRC
<whitequark>
but I see another problem: unlike atben, which uses SPI (am I right?) where you can just switch the clock with any scheduler-altered timings you like, in USB you has to do the switches and readings in a very timing-precise way
<whitequark>
I wonder if the stock (not rt) linux scheduler can handle that
<wpwrak>
whitequark: one problem is the LCD. if you don't turn it off, then you can't access memory. not sure if you can manage to run in cache without ill effects. the cache has a few special features that may help.
<DocScrutinizer>
wpwrak: not on my todo list
<whitequark>
wpwrak: huh, running from cache. that's way more MIPS magic than I really understand :/
<DocScrutinizer>
I'd think all USB cores allow the H and L trsts for D+/-
<wpwrak>
whitequark: you would do this like i did ubb-vga: turn off everything that could get in the way, then write compact code to bang the bits just at the right time
<DocScrutinizer>
also setting either line to H or L
<DocScrutinizer>
I'd need to eat the SOC's datasheet which I'm not going to do as I lost interest in the whole topic
<wpwrak>
DocScrutinizer: the 4720 has high-speed J and K (and Z) output, plus two higher-level tests (NAK and test packet)
<wpwrak>
DocScrutinizer: there's no input, though
<DocScrutinizer>
aaah J and K, not H and L
<whitequark>
wpwrak: what's the point of connecting HID devices without an LCD?
<wpwrak>
whitequark: well, you could just disable the LCD, get a quiet system, get your code to work, then see how you can make it survive concurrent system activity
<DocScrutinizer>
USB ransmission isn't usually a 100% of time job
<wpwrak>
DocScrutinizer: and being host-driven works in your favour there
<DocScrutinizer>
you may get away with stopping LCD for transmitting a packet over USB
<DocScrutinizer>
wpwrak: indeed
<DocScrutinizer>
simplifies things a lot
<DocScrutinizer>
my NASCOM-I also couldn't execute a single opcode on the CPU during display of a video line. Either had to live with the Hsync/Vsync timeslices, or you switched off video output
<DocScrutinizer>
iirc, or was that ZX81?
<wpwrak>
the ZX81 had this behaviour SLOW and FAST mode
<DocScrutinizer>
prolly ZX81, with the "fast" and "slow" cmd
<DocScrutinizer>
indeed
<DocScrutinizer>
:-D
<DocScrutinizer>
still ZX81 could do supertape ;-D
<DocScrutinizer>
ok, USB is a tad faster
<DocScrutinizer>
wpwrak: you're sure there's no diagnostics register here you can read back?
<DocScrutinizer>
doesn't make much sense to have J and K then, I guess
<wpwrak>
the USB standard requires that a device can enter those test modes on the host's request. seems that it's the host that does all the reading
<DocScrutinizer>
so what's that friggin IP core?
<DocScrutinizer>
please don't say Mentor ;-)
<wpwrak>
how do you tell ?
<DocScrutinizer>
haha
<DocScrutinizer>
honestly, what's the driver.ko's source header saying?
<wpwrak>
not sure if you understood my question. how do you find out what the origin of the IP core is ? except by looking at the data sheet, which i know you can't do
<wpwrak>
(looking at the data sheet and looking for a familiar pattern)
<wpwrak>
(if it just said "mentor", i would have told you :)
<DocScrutinizer>
uhm, lost me
<DocScrutinizer>
nm
<whooo>
hi, have anyone been able boot with an initramfs? or rather, to which address should I load it?
<rjeffries>
wpwrak one reason to find a way to leverage Ben USB cleint port as opposed to something on UBB 8"10 port is one wouold like to have atben radiop at same time as an external USB keyboard
<rjeffries>
so did someone say SIE may awaken, sans FPGA? that could be interesting in a hackerish way
<rjeffries>
if and only if it supports linux
<DocScrutinizer>
wpwrak: btw if I have had a look at Ben prior to "MP" then you bet we had those host pins on 2 pads next to the 0R bridges that connect USB receptacle to gadget pins
<DocScrutinizer>
unless somebody would have come up with "We don't need that" again and started arguing about the cost of 2pcs 0R
<DocScrutinizer>
:-S
<DocScrutinizer>
still wonders if wikireader still has footprint for a USB, or they "optimized" it out... "don't need that"
<DocScrutinizer>
wpwrak: watch out they don't optimize away your ext-ant footprint ;-)
<DocScrutinizer>
(bridges) might even have gotten footprint to get a twin-2way mux chip there
<wpwrak>
DocScrutinizer: (missing usb host signals) yeah, that's one of the sadder parts of the ben's hardware. i don't know if this was just overlooked or if there was a reason (such as lack of space)
<DocScrutinizer>
lack of space? c'mon
<DocScrutinizer>
I never bought the "lack of space" foo even for our GTA02 mods that got rejected using this lame argument
<DocScrutinizer>
always got parsed at my side as "we don't have enough space unless we would dare to touch the routing that we put so many days of work in"
<wpwrak>
well, i don't know the details of COB. if you say it can't create space issues, then they probably just overlooked it for no good reason
<whitequark>
DocScrutinizer: aren't complex things like openmoko or other phones routed automatically?
<DocScrutinizer>
remember A8? A7 even? No problem at all to move all the birdseed away from mic into the codec can. But when I asked for two testpoints: "Not enough space"
<DocScrutinizer>
whitequark: sure, like 80%
<DocScrutinizer>
still some days of work, but once you got the basic layout, small mods are no problem at all
<DocScrutinizer>
those router tools are pretty smart and mighty tools
<whitequark>
has routed all his boards manually. they were quite simple, through
<DocScrutinizer>
dunno ho wmuch of that power is usually really used by the average chinese layouter
<DocScrutinizer>
e.g we got zero design rule checks on GTA0x
<DocScrutinizer>
pretty bad
<wpwrak>
DocScrutinizer: you don't know half of what is possible on the darker side of chinese engineering ;-)
<DocScrutinizer>
sure it takes a bit longer to define DRC, but once they are defined, your duty becomes a lot easier
<DocScrutinizer>
wpwrak: I bet
<DocScrutinizer>
I'm even aware no 10 years at Taipei would suffice to learn all about that
<tuxbrain-mob>
wpwrak : what was the command to test the timings on the host?
<DocScrutinizer>
wpwrak: I just say "8*8 LED matrix with 64 series R"
<wpwrak>
DocScrutinizer: in hxd8, the folks from the US were complaining that someone had adjusted a bit of the layout by moving it ("drag and drop") to the desired location. what the didn't do was make sure things still connected where they should elsewhere and didn't make new connections where there should be none. naturally, no DRC was run. all those errors would have been just too confusing. and there goes another failed prototype run ...
<DocScrutinizer>
YAY!!!!!
<wpwrak>
DocScrutinizer: i think that was done by the fine folks fiwin had outsourced the layout to (before fiwin were killed and the project was merged into openmoko). so we never saw that sort of stuff at openmoko.
<wpwrak>
tuxbrain-mob: atrf-xtal 10000Â Â ?
<wpwrak>
DocScrutinizer: (8x8/64) that could be correct ... the real problem there was the absence of any specification of what that array should do. with the guy who "owned" the design refusing to explain. i don't blame the engineers for anything that happened there.
<wpwrak>
tuxbrain-mob: regarding the troublesome gpio test: there are two similar tests, one in P_ON state and the other in TRX_OFF. the one in TRX_OFF should be more predictable, but can test fewer things.
<wpwrak>
tuxbrain-mob: that's why i put most of the testing in the P_ON block. not that this one doesn't seem to work reliably, i'd propose the following:
<wpwrak>
tuxbrain-mob: 1) we ignore those problems in P_ON for now and i'll skip this test in the "atusb" script.
<wpwrak>
tuxbrain-mob: 2) i'll go over the TRX_OFF test and see if i can test more things, so that we're sure we don't have issues like shorted pins
<wpwrak>
tuxbrain-mob: 3) when i get my boards, i'll have a look at the P_ON test and see if i can figure out what went wrong there, and adapt the test if that makes sense.
<DocScrutinizer>
wpwrak: (with the guy owning design) LOL, indeed
<wpwrak>
tuxbrain-mob: i.e., the failure probably just indicates me misunderstanding some property of the system that's not relevant for operation.
<tuxbrain-mob>
wpwrak just tellme what to do and i will
<wpwrak>
tuxbrain-mob: for now, just don't run the test on all the boards yet, because i'll probably make a few small changes
<wpwrak>
tuxbrain-mob: meanwhile, you can set up the spectrum test and see if the sugru works
<tuxbrain-mob>
remember i will start the mass test tomorrow, no sugru here now :( , sorry for the push but I'm really scheduleballsclamped
<tuxbrain-mob>
if i do not test this weekend i don't know when i will have another big time window aviable to retake it
<wpwrak>
tuxbrain-mob: tomorrow = monday ? :) that's plenty of time ;-)
<tuxbrain-mob>
ok not tomorrow, today after a few hours of sleep
<wpwrak>
tuxbrain-mob: ah, and there's new firmware. i also changed the boot loader. lots of things have changed inside: it now uses interrupts instead of polling, i fixed a number of small races in the USB driver, and - most importantly - i extended the boot loader delay from ~2.0 s to 2.5 s.
<tuxbrain-mob>
well i have not reflashed anymore but the first one so no problem
<tuxbrain-mob>
just sendme the links by email pleease
<wpwrak>
the current boot loader delay could become a problem when using dfu-util without prior reset. perhaps you remember the discussion with Stefan ? i've implemented that mode now. the old boot loader usually worked, but that was more by luck than by design (probably because some other changes made the loop take a little longer than 2.00 seconds)
<wpwrak>
i'll play with things a little more and then make the "final" firmware images and announce them on the list
<wpwrak>
ah, but in case you want to play ... lemme upload them ...
<tuxbrain-mob>
ok I hope this final one comes along the week i will reconnect with you tomorrow when i have a bunch of atben atusb depanelized and ready to flash to know if the firmware is also ready
<wpwrak>
tuxbrain-mob: stop music players, video, etc. don't load web pages or move windows while testing
<tuxbrain-mob>
I have killed all  X to obtain this results, just the console
<wpwrak>
tuxbrain-mob: if this still doesn't help, i can add some more filtering to atrf-xtal
<wpwrak>
okay, that's bad then
<DocScrutinizer>
wpwrak: though there are brilliant dudes that need only one R for 36 diodes :-o operated from a 3.6V LiIon
<wpwrak>
you can try collecting more samples. but that will also make the test slower
<wpwrak>
or defer the test until you're back at a proper pc :)
<wpwrak>
your laptop probably doesn't have a cleanly ntp-disciplined clock either now, so the measurements would be questionable at best
<wpwrak>
DocScrutinizer: oh, if all the LEDs are on all the time, that ought to work, too. that is, unless something goes wrong. after that, tepco :)
<DocScrutinizer>
hehe, yeah
<tuxbrain-mob>
ntp is installed will the 3g connection affect this ntp thing?
<DocScrutinizer>
just adopted tepco for a generic descriptive term of a class of events
<wpwrak>
tuxbrain-mob: probably. i don't know how much, but i can't imagine ntpd will stabilize very quickly in this scenario.
<whitequark>
DocScrutinizer: will that really work as intended? all LEDs have a bit different VAC, AFAIK, and the ones with lowest forward voltage will be brightest (and hottest), and all others will be quite dim
<DocScrutinizer>
yes
<DocScrutinizer>
I think it's BS design
<wpwrak>
DocScrutinizer: the russians will be angry. now nobody honors the skills demonstrated at chernobyl anymore.
<DocScrutinizer>
hehehe
<whitequark>
wpwrak: "tepco" as adjective is brilliant!
<whitequark>
DocScrutinizer: what's BS? that abbreviation may have a dozen of meanings
<whitequark>
no one needs step-down when you can just put a resistor
<wpwrak>
tuxbrain-mob: if you want to experiment a bit, you can try to set up dirtpan. if you generate a lot of traffic, your connections will eventually hang, because there's no CSMA and you just drive up TCP timeouts. but it should be good for a few tests.
<DocScrutinizer>
I'd rather use step-up here, to something like 30V, then use 3..4 chains with one series R each
<wpwrak>
tuxbrain-mob: ah, and in the commercial description, the available flash size will go down a little. all the code improvements ate a bit of space. i'll update this in a bit as well.
<whitequark>
DocScrutinizer: is that for minimizing the DC-DC converter current?
<DocScrutinizer>
or use unlimited step-up regulated vie current-feedback, one chain, no series R
<DocScrutinizer>
that's for minimizing the loss on mandatory series R
<DocScrutinizer>
there actually are "designs" that come with no (visible) series R at all, but that's really poor stuff
<DocScrutinizer>
frequently keychain crap with one CR2032 and one LED is of that class