<wolfspraul>
can we have some way to put the m1 into an 'automatically boot' mode?
<wolfspraul>
it would probably require a modification in the standby bitstream
<wolfspraul>
maybe some setting one has in the gui, to enable/disable auto-boot?
<wolfspraul>
actually thinking about this more, wouldn't most people who power-up their m1 want to boot anyway?
<wolfspraul>
maybe the default should be to auto-boot
<kristianpaul>
you mena avoid to press middle buttong after plug power cord?
<kristianpaul>
enable/disable may be will be achieved by flashing the current standby bitstream and the automatic boot one when disable?
<wolfspraul>
huh?
<wolfspraul>
don't understand :-)
<wolfspraul>
yes, I mean no need to press middle button
<wolfspraul>
just skip that and boot automatically
<wolfspraul>
maybe controlled by a setting in the gui, but now I think even by default it can just do that
<wolfspraul>
the use cases of most people are such that they plug in/power m1 to start rendering, always
<kristianpaul>
he, i mean, we can have two standby bitstream, one for automatically boot other for classic standby boot
<wolfspraul>
I'm mostly interested in the behavior of the boxes I ship
<wolfspraul>
right now it's just a question - wouldn't it make more sense to automatically boot by default?
<wolfspraul>
in the use cases I have seen so far, my answer would be: yes
<wolfspraul>
maybe there is a law somewhere that makes this 'illegal' for environmental reasons?
<wolfspraul>
wasting energy is not good of course, if it ran silently that would be bad too
<wolfspraul>
well, just thinking
<wpwrak>
wolfspraul: power on to boot makes a lot of sense to me :)
<wpwrak>
one problem may be how to distinguish power off (i.e., stay quiet until middle button) from power on
<wolfspraul>
maybe it should just never be in this state? :-)
<wpwrak>
dunno if it has any power advantages
<wpwrak>
but yes, i sometimes wonder myself :)
<wolfspraul>
we do need to fix the last power-off weaknesses for that though
<wolfspraul>
we cannot recommend a workaround (software power off), and then remove that workaround
<wolfspraul>
nobody will follow that recommendation anyway
<wpwrak>
yeah :)
<wpwrak>
of course, they have a ~one in 500 chance to get it right :)
<wpwrak>
which, according to murphy, means that disaster will inevitably on the first important event
<wpwrak>
s/on/strike on/
<wpwrak>
and afaik, this recommendation hasn't really been communicated either :)
<wolfspraul>
I won't even try, we have zero chance to get people to follow
<wolfspraul>
I need to focus on the "press middle power button to boot" message :-)
<wpwrak>
hmm, some will. especially after the first mishap
<wolfspraul>
nah. locking makes it safe enough.
<wpwrak>
yes. "middle button to boot" is bad.
<wpwrak>
maybe it exists to have a means to select rescue
<wpwrak>
of course, the same could be accomplished by changing the path to rescue from a button combination to "plug in power while pressing button"
<wolfspraul>
yes
<wpwrak>
i would also love to have a lot more interaction on the display. OSD feedback on actions and such. of course, you'd drop all this for performance, but while getting to know the machine, it's not nice for it to operate in "expert mode"
<wpwrak>
in other words, i wish we had some people who'd like to get their hands dirty with the GUI :)
<sb0>
the main priority, usability-wise, is to get GOOD video tutorials and demos atm
<sb0>
the current videos are lousy, which both gives a bad impression about the product and doesn't explain much
<sb0>
I'm going to a small studio on Friday and try to improve that
<sb0>
....
<wolfspraul>
sb0: perfect!
<wolfspraul>
unboxing video would be great too
<sb0>
this is what I plan on doing
<wolfspraul>
I haven't checked the masala video links you posted once because you said only 1/3rd of the screen is visible and better ones are coming
<sb0>
plus footage with VGA grabber + camera setup, hopefully a good one
<sb0>
yes this masala stuff is lost in slowland
<wolfspraul>
also agata hasn't replied about video links from masala or masecki yet, oh well
<wolfspraul>
sb0: ok I'm making some progress on review units
<wolfspraul>
first of all tuxbrain has agreed to be a hub for a review unit (or several if we become that popular)
<wolfspraul>
an EU hub
<wolfspraul>
so shipments will be fast and cheap, and easy for EU people to return
<wolfspraul>
then tuxbrain still has two rc2 boards he never sold, and I will buy them back
<wolfspraul>
Adam will apply all of the important fixes to them including wolfson codec, then those 2 boards turn into review unit boards
<wolfspraul>
that way we solve several problems at once
<wolfspraul>
tuxbrain avoids a loss, sells back to me
<wolfspraul>
we improve the quality of those 2 boards
<wolfspraul>
we use them as review units
<wolfspraul>
etc.
<sb0>
this will take weeks... can you ship a rc3 to the UK right now?
<wolfspraul>
I was planning to use the returned rc2 review unit for that
<wolfspraul>
we cannot make it in time for China Music anyway, tuxbrain sends tomorrow with fedex, the review unit should be in the UK end of next week
<sb0>
grmbl
<sb0>
delays
<wolfspraul>
did you demo m1 to massimo already?
<sb0>
no, it was just a quick meeting
<sb0>
he just saw it, but not running
<sb0>
if we ship the unit now instead of waiting for rc2 to come back, rework, packaging, etc. we can make it in time
<wolfspraul>
maybe, but it feels wasteful. I am trying to speedup everything but wasting resources is not a good approach imo.
<wolfspraul>
what is the connection between the unit arriving in the UK to be reviewed by his partner and him traveling to China Music?
<wolfspraul>
I dont' understand how those 2 things are related.
<wolfspraul>
how about your m1 unit? that's probably the fastest to get to the UK :-)
<sb0>
well I guess that will be the solution
<wolfspraul>
I thought you try to sell it, but if you start using it then after some time it's not in sellable condition anyway.
<wolfspraul>
what is the plan with that unit?
<wolfspraul>
maybe you should have two in general
<wolfspraul>
one in perfect condition to sell, another one to show/demo or borrow out
<sb0>
I use it and demo it to people. including showing the packaging
<wolfspraul>
good
<wolfspraul>
the problem in borrowing out is the followup
<wolfspraul>
and getting it back in good condition or at all
<wolfspraul>
which is also not so much a financial problem, but the problem is unless you followup, things just disappear and *nobody* benefits
<wolfspraul>
lesson #1 in economics: anything that is free will be wasted
<wolfspraul>
:-)
<wolfspraul>
so that's the hard part, to followup and make sure it's used for something good
<wolfspraul>
I have a solid plan now on those 2 review units, and rushing as much as possible
<wolfspraul>
david will fedex tomorrow
<wolfspraul>
adam has all parts ready
<wolfspraul>
many good problems are being taken care of at once
<wolfspraul>
what is the connection between the UK review unit and the China trip?
<sb0>
he just said he would prefer that. ask him for details
<sb0>
in either case, not being slow is god
<wolfspraul>
you bet
<wolfspraul>
that's why we send everything with fedex
<wolfspraul>
and even priority on the 10kg and 25kg boxes
<wolfspraul>
you can send your unit
<wolfspraul>
you should have 2 units
<wolfspraul>
purpose: one for sale (perfect condition), one for demo/borrow
<wolfspraul>
no?
<wolfspraul>
the reason you should have one for sale is that you can filter people :-)
<wolfspraul>
buy or shut up
<wolfspraul>
meeting only if you buy in cash at the meeting
<wolfspraul>
seriously
<wolfspraul>
you can do those things only if you have a perfect unit for sale
<sb0>
ok i will go to fedex this afternoon
<sb0>
technical progress? that's more a problem for xilinx
<wolfspraul>
I mean comparison with more megahertz, megabytes, mega-everything
<wolfspraul>
wpwrak: how about this CE0 and we_n pullup thing?
<wolfspraul>
is that someone we can or should rework? do any tests with?
<wolfspraul>
sb0: what do you think?
<wpwrak>
see my reply on the list ;-)
<wolfspraul>
yes I saw it
<wpwrak>
i think it makes sense. don't know if this helps in this specific case, but it very well might
<wolfspraul>
my question is more practical - can this be added on the rc3 boards?
<wolfspraul>
can you try with your board and rerun some tests? parts missing?
<wolfspraul>
should Adam test something?
<wpwrak>
lemme have a peek ...
<wpwrak>
WE# is relatively easy to access near the NOR. CE0 harder. let's see where they are on the FPGA side.
<wpwrak>
unfriendly on the FPGA side
<wpwrak>
now, let's look at the real PCB ...
<wpwrak>
yeah, should be possible to rework it with 0402 parts. there's also access to 3.3 V nearby on both cases. connecting it will be a little messy
<wpwrak>
do i have 4k7 at 0402 ... checking ... yes. a whole vial full of them :)
<wpwrak>
but before trying such a rework, i want to bring the testing process more under control. it still runs away too often for my taste. more control means accelerating it to reduce the risk of getting outliers that take a week of hammering before they show up, and also controlling the temperature
<wpwrak>
not quite sure yet whether i'll try air conditioning or go straight for the fridge
<wpwrak>
probably best to set up air conditioning and measure whether the temperature really stays reasonably constant (and low) throughout the day
<wolfspraul>
wpwrak: hmm, ok good
<wolfspraul>
so what are the next steps?
<wpwrak>
tomorrow, my guest room will be available for air conditioning experiments. so i'll set the AC to 18 C, and check the temperature every hour or so.
<wpwrak>
wiring up the fridge probably has to wait until next week (or, if the air conditioning performs well, i'll then move the M1 over there).
<wolfspraul>
should we ask Adam about trying this rework?
<wpwrak>
i also need to automate the "did it boot" check, which currently involves me looking at the LEDs
<wolfspraul>
or is it not so urgent and you will investigate on your side first then we approach adam later?
<wpwrak>
hmm, you can ask him what he thinks about doing this on a number of devices
<wpwrak>
i think the torture-testing is easier on my side, because i can automate it
<wolfspraul>
so the question is whether we can add a 4.7k pullup on ce0 and we# ?
<wpwrak>
yes, and whether adam things it will stay there :) (mechanically)
<wpwrak>
and the question on my side would be to see if it actually makes a difference
<wolfspraul>
we can also just schedule it for rc4
<wolfspraul>
or only one of the two, if that is easier on rc3 and still makes a positive impact
<wpwrak>
that would depend on adam's verdict. if he doesn't like it for rework risk, overhead, or reliability, then it would become an rc4 item
<wpwrak>
if he's happy to mass-rework, we need to check if it actually accomplishes anything
<wpwrak>
well, if he's VERY happy to mass-rework, we can just do it if it doesn't make things worse ;-)
<GitHub64>
[llvm-lm32] jpbonn pushed 390 new commits to master: http://git.io/NwEHzQ
<GitHub64>
[llvm-lm32/master] Synthesize SSE3/AVX 128 bit horizontal add/sub instructions from - Duncan Sands
<GitHub64>
[llvm-lm32/master] Add a MinNumRegs argument to MRI::constrainRegClass(). - Jakob Stoklund Olesen
<GitHub64>
[llvm-lm32/master] Constrain register classes instead of emitting copies. - Jakob Stoklund Olesen
<GitHub133>
[clang-lm32] jpbonn pushed 564 new commits to master: http://git.io/pIH7ng
<GitHub133>
[clang-lm32/master] Fix debug info encodings for char16_t and char32_t. - Devang Patel
<GitHub133>
[clang-lm32/master] [analyzer] Test for -analyze-function on ObjectiveC to accompany r139439. - Anna Zaks
<GitHub133>
[clang-lm32/master] [analyzer] Fix a new failure encountered while building Adium exposed as a result of r138196(radar://10087620). ObjectiveC property of type int has a value of type ObjCPropRef, which is a Loc.  - Anna Zaks