#2169: mokomakefile/org.openmoko.asu.stable: illume_svn.bb do_fetch failed
-+--
Reporter: lindi| Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone
[ I hope you don't mind if I copy the "devel" list where this discussion
started. Chances are that others are interested in this as well, and
this gives them a chance to read it or to find the topic with a search
engine. ]
Sreeraj a wrote:
> you guessed right. I want my neo -> debugBoard to
Graeme Gregory wrote:
> As for git hosting I'm sure we can organise that within OM. I have the
> resources to host it myself but better to get OM to do it :-)
I wonder if this is something projects (Gforge) could offer. Since git
has become fairly popular for Open Source projects and particularly
Thomas White wrote:
> Many people have (rightly) pointed out that 3D acceleration isn't
> something that OM themselves should be spending time and money on, so
> this part is purely a community project. Despite the fact that Glamo
> won't be being used in future devices, there are people (such as
> > I'd like to ramp-up to speed ASAP so that I know which parts to
> > focus on.
Hi there - thanks for signing up! We certainly need as many keen
people as possible for this project. If I've found out only one thing
since trying to contribute here, it's that it's very difficult to get
informati
#2169: mokomakefile/org.openmoko.asu.stable: illume_svn.bb do_fetch failed
-+--
Reporter: lindi| Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone
Christopher Friedt wrote:
> Hi Graeme,
>
> I've recently 'signed up' to work on xglamo as well - under NDA - so
> I have access to the documentation. I presume that you do as well.
>
> I'd like to ramp-up to speed ASAP so that I know which parts to focus
> on. I've just checked out the xorg-driver
On Sun, 2009-01-04 at 21:17 +1030, Rod Whitby wrote:
> digger vermont wrote:
> > On Fri, 2009-01-02 at 19:03 +1030, Rod Whitby wrote:
> >> The README on downloads.freesmartphone.org will point you to the build
> >> logs, from where you can determine which OE packages are causing the
> >> builds t
Well over xmas/new year I managed to finish porting the code from kdrive
to xorg architecture. The code is still contained in the
xora/xorg-driver-wip branch as it is not currently functional.
As can be seen from the log below we successfully initialise the exa
extension but the first time we try
Hi All,
it's been a long time since we have had an update on the GSM Firmware
update (moko10 of 11). It was told that a boot image would be proposed
to allow safe update. Any status on that would be nice.
Thanks,
Nicolas
___
devel mailing list
devel@lis
Sreeraj a wrote:
> specifically, how to use the JTAG pins as I/O pins.
Do you want to interface PC->debugv3->I/O or Neo->debugv3->I/O ?
The Neo can't really control the JTAG signals. But I2C, SPI, etc.
are accessible. (J10 and J11) The schematics of the board are here:
http://people.openmoko.org
digger vermont wrote:
> On Fri, 2009-01-02 at 19:03 +1030, Rod Whitby wrote:
>> The README on downloads.freesmartphone.org will point you to the build logs,
>> from where you can determine which OE packages are causing the builds to
>> fail. Then you can raise bug reports for those failures and
Mark Chandler wrote:
> Rod - may I ask what's wrong with your moko? If it's a h/w issue, I'd be
> glad to send you either my 1973 or FreeRunner.
I have a pre-release US FreeRunner which, irrespective of having an
externally fully charged battery, only decides to turn on once in
between 50 and 200
Hi,
I have been trying to do some hardware interfacing using my neo 1973's JTAG
board, but couldnot find any documentation regarding it.
specifically, how to use the JTAG pins as I/O pins.
is there any documentation on how to use the board for simple led-blinkning
stuff?
Thanks in advance
sreeraj
14 matches
Mail list logo
