Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Dave Neary schrieb: > Hi, > > Faheem Pervez wrote: >> You sure you have a choice in the matter? Considering how you're >> already violating the GPL. > > I don't know the details of the situation. I just want to remind you > that the GPL is a distribution licence. That's why we don't get all > Google's changes to the Linux kernel and Apache back upstream. It seems Well, Google publishes all the sources, see http://android.git.kernel.org/ This git seems impressively complete. But this is OT here since we are talking about Nokia/Maemo. Concerning obligations, Nokia nor anyone else is obliged by the license to push changes upstream - it is just good practise. You only have to give access to the changes or the whole (modified) source package, which Nokia in 99.9% of the cases properly did and which Google using the git, as far as we can tell from just looking at it, also did. What we can really moan and complain about is the lack of good practise with some businesses, since already mentioned, e.g. Google. They did a pretty bad job in working *together* with the communities to get their thing done. This is quite in contrast with Nokia which collaborated quite well from the very early beginning of the Maemo project. There is always room for improvement, but hey... But what really sucks badly is the tivolization taking place especially in the mobile phone area, where you get all the sources (due to license) and probably most of the tools but you f*ckn' cannot get a modified version of some part onto the device. This *really* sucks! And frankly it really hurts me. (For the Google stuff by some lucky coincidence the engineering bootloader leaked and a way to "root" the device but this was not intended neither by Google, HTC nor T-mobile). And here Nokia again is a little more open than many others by providing the flasher util, which basically allows you to install anything onto your tablet. I sincerely hope that this openness continues when Nokia releases Linux based mobile phones some day... > that I've seen people say that Nokia doesn't even distribute the initfs > tools. If that's the case, there wouldn't be any GPL violation. I might be wrong here but I am pretty sure that the GPL also requires you to give access to the tools that were used to generate the shipped version from the (L)GPLed sources. A little more specifically see: http://www.softwarefreedom.org/resources/2008/compliance-guide.html section 4.2.3 So you need at least have to say which *exact* tools were used and how they were used to produce the binary you shipped. So you do not necessarily have to directly supply them but you have to exactly name them and the way they ought to be used to reproduce the binary you shipped. Well, fair enough... I would also expect, though it is not mentioned there directly, that those tools have to available to everyone - with a price-tag maybe, but must be available. > Cheers, > Dave. Cheers nils faerber -- kernel concepts GbRTel: +49-271-771091-12 Sieghuetter Hauptweg 48Fax: +49-271-771091-19 D-57072 Siegen Mob: +49-176-21024535 http://www.kernelconcepts.de ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Oops. Forgot to CC him. On Thu, 2009-07-02 at 14:33 +0200, ext e...@okerson.com wrote: > > Hi, > > > > Faheem Pervez wrote: > >> You sure you have a choice in the matter? Considering how you're > >> already violating the GPL. > > > Dave Neary wrote: > > I don't know the details of the situation. I just want to remind you > > that the GPL is a distribution licence. That's why we don't get all > > Google's changes to the Linux kernel and Apache back upstream. It seems > > that I've seen people say that Nokia doesn't even distribute the initfs > > tools. If that's the case, there wouldn't be any GPL violation. > > But Google isn't distributing their Linux Kernel or Apache, Nokia is > distributing the initfs. Which is why Nokia is violating the GPL (I haven't checked myself that code is not being distributed for stuff in initfs). I'd say the best option is to poke Quim Gil as I assume he's the correct person to handle this (I'm CC'ing him although I assume he reads this list). Cheers, -- Maemo Software Nokia Devices ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Thu, 2009-07-02 at 14:33 +0200, ext e...@okerson.com wrote: > > Hi, > > > > Faheem Pervez wrote: > >> You sure you have a choice in the matter? Considering how you're > >> already violating the GPL. > > > Dave Neary wrote: > > I don't know the details of the situation. I just want to remind you > > that the GPL is a distribution licence. That's why we don't get all > > Google's changes to the Linux kernel and Apache back upstream. It seems > > that I've seen people say that Nokia doesn't even distribute the initfs > > tools. If that's the case, there wouldn't be any GPL violation. > > But Google isn't distributing their Linux Kernel or Apache, Nokia is > distributing the initfs. Which is why Nokia is violating the GPL (I haven't checked myself that code is not being distributed for stuff in initfs). I'd say the best option is to poke Quim Gil as I assume he's the correct person to handle this (I'm CC'ing him although I assume he reads this list). Cheers, -- Maemo Software Nokia Devices ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, >-Original Message- >From: ext Frantisek Dufka [mailto:duf...@seznam.cz] >Sent: 02 July, 2009 15:54 >To: Dave Neary >Cc: Faheem Pervez; maemo-developers@maemo.org; Tikka Jarmo >(Nokia-D/Helsinki) >Subject: Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for >Fremantle and Diablo released > >Dave Neary wrote: >> I've seen people say that Nokia doesn't even distribute the initfs >> tools. If that's the case, there wouldn't be any GPL violation. > >Let's move detailed discussion back to the bug report. Please do :). Especially if there are any Nokia modified open source (GPLed that requires sources to be published) packages that we do not have sources available from SDK repository just file bug reports about those. This initfs has been somewhat problematic as it's components have not been part of rootfs or kernel for which maemo SDK team ahs provided sources from SDK repository. Because we have not had official toolchain for initfs development SDK team has not (if you so say) published all OSS components from it. This will most probably be fixed with Fremantle as now initfs components are part of rootfs (e.g. SDK rootstraps) and I think we have sources for all SDK rootstrap components in SDK repository. > >Quick and hopefully correct summary is that Nokia is >distributing modified uclibc (EABI patched 0.9.28) so we >should get at least exact uclibc sources used for building >initfs. That is indeed enough to satisfy GPL and also to close >the bug report since we can rebuild gcc with such uclibc and >make the toolchain ourselves. Write one bug report for each final platform release about GPLed components that you think are modified by Nokia but sources are not available from maemo.org to the maemo bugzilla. If those components are in initfs our platform teams probably need to release sources in some separate packages because we in SDK team construct our SDK rootstraps by rebuilding them from scratch and initfs components are not part of that process in Diablo (but should be in Fremantle). > >uclibc is IMO really the tricky part, PCMIIAW but 0.9.28 does >not support EABI out of box, there are several (maybe >incomplete) patches to add EABI support to 0.9.28 mentioned in >uclibc mailing list so it is quite hard to decide which >specific version (if any) went into the binary which is >distributed with the tablets. Just add uclibc into that bug report for Diablo platform release. If you find similar packages from SDK (there really should not be any as I really think we release all sources for all SDK OSS components) write separate bug report for Diablo SDK because Diablo plaform in device and Diablo SDK are separate products. > >The original request is for toolchain binary since my idea was >that it is easier for both sides (the binary exists inside >Nokia - name was mentioned is OS2007 hacker edition guide, and >hopefully there is no reason to keep the sources or binaries >of gcc closed). If we have modified some OSS components and deliver binaries as part of our products (platform and SDK) we release also modified sources for them. Just write bug reports about them. Still I do not think we will release any new toolchains for Diablo as toochains are part of SDK product and need to be tested and documented and ... Cheers, //Jarmo > >Frantisek > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Dave Neary wrote: > I've seen people say that Nokia doesn't even distribute the initfs > tools. If that's the case, there wouldn't be any GPL violation. Let's move detailed discussion back to the bug report. Quick and hopefully correct summary is that Nokia is distributing modified uclibc (EABI patched 0.9.28) so we should get at least exact uclibc sources used for building initfs. That is indeed enough to satisfy GPL and also to close the bug report since we can rebuild gcc with such uclibc and make the toolchain ourselves. uclibc is IMO really the tricky part, PCMIIAW but 0.9.28 does not support EABI out of box, there are several (maybe incomplete) patches to add EABI support to 0.9.28 mentioned in uclibc mailing list so it is quite hard to decide which specific version (if any) went into the binary which is distributed with the tablets. The original request is for toolchain binary since my idea was that it is easier for both sides (the binary exists inside Nokia - name was mentioned is OS2007 hacker edition guide, and hopefully there is no reason to keep the sources or binaries of gcc closed). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
> Hi, > > Faheem Pervez wrote: >> You sure you have a choice in the matter? Considering how you're >> already violating the GPL. > Dave Neary wrote: > I don't know the details of the situation. I just want to remind you > that the GPL is a distribution licence. That's why we don't get all > Google's changes to the Linux kernel and Apache back upstream. It seems > that I've seen people say that Nokia doesn't even distribute the initfs > tools. If that's the case, there wouldn't be any GPL violation. But Google isn't distributing their Linux Kernel or Apache, Nokia is distributing the initfs. Ed Okerson ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, I'm certainly far from being a licensing expert. But there is a paragraph on a page at the busybox site which does make it clear wrt busybox and releasing source: http://www.busybox.net/license.html I see a /mnt/initfs/bin/busybox but I don't see the source available for the busybox 1.00 used in the initfs. But Mohammed's reply on the bug in question does give me a little more hope. Best Regards, Faheem On 7/2/09, Dave Neary wrote: > Hi, > > Faheem Pervez wrote: >> You sure you have a choice in the matter? Considering how you're >> already violating the GPL. > > I don't know the details of the situation. I just want to remind you > that the GPL is a distribution licence. That's why we don't get all > Google's changes to the Linux kernel and Apache back upstream. It seems > that I've seen people say that Nokia doesn't even distribute the initfs > tools. If that's the case, there wouldn't be any GPL violation. > > Cheers, > Dave. > > -- > maemo.org docsmaster > Email: dne...@maemo.org > Jabber: bo...@jabber.org > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, Faheem Pervez wrote: > You sure you have a choice in the matter? Considering how you're > already violating the GPL. I don't know the details of the situation. I just want to remind you that the GPL is a distribution licence. That's why we don't get all Google's changes to the Linux kernel and Apache back upstream. It seems that I've seen people say that Nokia doesn't even distribute the initfs tools. If that's the case, there wouldn't be any GPL violation. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
(Well, s/you/Nokia/) On 7/2/09, Faheem Pervez wrote: > You sure you have a choice in the matter? Considering how you're > already violating the GPL. > > On 7/2/09, jarmo.ti...@nokia.com wrote: >> And I do not >> belive we have any plans to release toolchain for initfs development for >> Diablo anymore. >> >> Cheers, >> //Jarmo >> ___ >> maemo-developers mailing list >> maemo-developers@maemo.org >> https://lists.maemo.org/mailman/listinfo/maemo-developers >> > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
You sure you have a choice in the matter? Considering how you're already violating the GPL. On 7/2/09, jarmo.ti...@nokia.com wrote: > And I do not > belive we have any plans to release toolchain for initfs development for > Diablo anymore. > > Cheers, > //Jarmo > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, >-Original Message- >From: ext Frantisek Dufka [mailto:duf...@seznam.cz] >Sent: 02 July, 2009 09:46 >Fremantle and Diablo released > >jarmo.ti...@nokia.com wrote: > >> BTW I think flasher is the only closed source tool we have >in maemo development environment. Or at least I do not know >any other binary only tool :). >> > >I think gcc/uclibc toolchain for initfs development would >qualify but it is much worse here, we even don't have the tool >(despite GPL) :-( > >https://bugs.maemo.org/show_bug.cgi?id=3373 Good point and there actually are even more "closed" tools or tools that we do not publish in maemo.org but we use internally to develop certain components (especially for those that are very close to the HW as they may require HW vendor toolchain to be used). When I said that we do not have other closed tools in maemo than flasher I ment tools that we publish in maemo.org. For initfs development (and development of some very hw related components like DSP, codecs, driverts,...) these have never been supported officially in maemo and so we have not released toolchain for them either. There were plan to start supporting initfs development as we already support development of rootfs components and kernel/kernel modules but as Fremantle does not have initfs anymore these plans were not implemented. And I do not belive we have any plans to release toolchain for initfs development for Diablo anymore. Cheers, //Jarmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
closed tools, Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
jarmo.ti...@nokia.com wrote: > BTW I think flasher is the only closed source tool we have in maemo > development environment. Or at least I do not know any other binary only tool > :). > I think gcc/uclibc toolchain for initfs development would qualify but it is much worse here, we even don't have the tool (despite GPL) :-( https://bugs.maemo.org/show_bug.cgi?id=3373 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Thu, Jul 2, 2009 at 1:36 AM, Ryan Abel wrote: > On Wed, Jul 1, 2009 at 3:44 PM, Kees > Jongenburger wrote: >>> There's absolutely no reason why not. Really, though, why don't we just open >>> source it so we don't have to deal with ANY of this insanity? >> >> There are other project the 0x flasher out there and not enough people >> tried and used it so what is the point? >> > > Define "enough", please. I've certainly seen plenty of people getting > good use out of it, so it certainly seems like "enough" to me. If > you're expecting a mass migration from a functional, tested > manufacturer-provided to an 3rd-party solution of unknown quality > which provides little in the way of additional features, well, of > course it's not going to be "enough". What are you missing and why didn't *you* add it? that is the question that you need to answer for yourself before making such statements. > > Really, the right question to be asking is "Why not?". The > justifications should be for keeping things closed, not making them > open. This is not the way we haven been working in the last year or so. We can create fair request to open component and Nokia can take them into account. I was able to use 0x to render my device usable after flashing a self modified image so I am very happy the alternative exists. Being able to create fiasco images (using specs) can also be nice for Mer. Greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, Some comments about opnesourcing flasher code below. BTW I think flasher is the only closed source tool we have in maemo development environment. Or at least I do not know any other binary only tool :). >-Original Message- >From: ext Hubert Figuiere [mailto:h...@figuiere.net] >Sent: 01 July, 2009 20:06 >Subject: Re: Maemo Flasher-3.5 Tool Beta for Fremantle and >Diablo released > >On 06/30/2009 08:41 AM, jarmo.ti...@nokia.com wrote: >> The Maemo Eclipse Integration 2nd Edition project has >released installation packages for Maemo Flasher-3.5 Tool Beta >for Linuxes, Mac OS X and Windows. Maemo Flasher-3.5 tool >supports flashing of N8x0 Diablo devices and coming Fremantle devices. >> > >Any plan to release the source code of the Flasher? Sorry no plans for that. I think the main reason being that we use some 3rd party interfaces that cannot be published and because of that propably also some source code. This is also business related issue as being able to freely update maintenance releases is of course the standard way of working but in commercial world being able to flash freely also new platform release to old hw (as we have provided in many cases) is not the standard way how or competitors work mainly befouse it is a lot of work to support old hw. Cheers, //Jarmo > > >Hub > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Wed, Jul 1, 2009 at 3:44 PM, Kees Jongenburger wrote: >> There's absolutely no reason why not. Really, though, why don't we just open >> source it so we don't have to deal with ANY of this insanity? > > There are other project the 0x flasher out there and not enough people > tried and used it so what is the point? > Define "enough", please. I've certainly seen plenty of people getting good use out of it, so it certainly seems like "enough" to me. If you're expecting a mass migration from a functional, tested manufacturer-provided to an 3rd-party solution of unknown quality which provides little in the way of additional features, well, of course it's not going to be "enough". Really, the right question to be asking is "Why not?". The justifications should be for keeping things closed, not making them open. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi Ryan On Wed, Jul 1, 2009 at 4:06 PM, Ryan Abel wrote: > (Sorry for the terrible quoting. You all knoe exactly how useless an > application Modest is. :)) Still not acceptable > > There's absolutely no reason why not. Really, though, why don't we just open > source it so we don't have to deal with ANY of this insanity? There are other project the 0x flasher out there and not enough people tried and used it so what is the point? Greetings ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
*If* Nokia have no intention of open-sourcing this version of the flasher (because it can flash the new "tablet" and Nokia may not like the idea of releasing code relating to the internals of the new "tablet"), then I'd sincerely hope that they would at release the code to 3.0 as Nokia (yes, I mean Nokia: I'm not referring to Mer here) have no intention of providing updates for the devices flasher-3.0 supports (not bitter about it in any way - I'm just telling it as a statement of fact), it would be nice to have the source code to that version. Of course: Only if this version or the latest final version - whatever that may be - can't be open-sourced for whatever reason. Best Regards, Faheem On 7/1/09, Hubert Figuiere wrote: > On 06/30/2009 08:41 AM, jarmo.ti...@nokia.com wrote: >> The Maemo Eclipse Integration 2nd Edition project has released >> installation packages for Maemo Flasher-3.5 Tool Beta for Linuxes, Mac OS >> X and Windows. Maemo Flasher-3.5 tool supports flashing of N8x0 Diablo >> devices and coming Fremantle devices. >> > > Any plan to release the source code of the Flasher? > > > Hub > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Am Mittwoch, den 01.07.2009, 13:06 -0400 schrieb Hubert Figuiere: > Any plan to release the source code of the Flasher? Also see a thread from November/December 2008: http://lists.maemo.org/pipermail/maemo-community/2008-November/001367.html http://lists.maemo.org/pipermail/maemo-community/2008-December/001396.html andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On 06/30/2009 08:41 AM, jarmo.ti...@nokia.com wrote: > The Maemo Eclipse Integration 2nd Edition project has released installation > packages for Maemo Flasher-3.5 Tool Beta for Linuxes, Mac OS X and Windows. > Maemo Flasher-3.5 tool supports flashing of N8x0 Diablo devices and coming > Fremantle devices. > Any plan to release the source code of the Flasher? Hub ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, [jot] some answers below... From: ext gary liquid [mailto:liq...@gmail.com] Sent: 01 July, 2009 15:58 To: Ryan Abel Cc: Tikka Jarmo (Nokia-D/Helsinki); maemo-us...@maemo.org; maemo-developers@maemo.org Subject: Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released is it possible to do tablet->tablet flashing? (serious question) [jot] I think it is not possible because Tablet USB port drivers do not support it but I am not sure. What is possible is to use /usr/sbin/fiasco_flasher available from Tablet to flash images from mmc card. most of us now have more than one device and since not all of us have linux or windows available (hiya GA), having a native solution would be a possible quicker workaround [jot] The easies way to do flashing we be from PC but maybe it would be enough for you to flash from inside Tablet. BTW no quarantine this will work as I have not tested this myself. Cheers, //Jarmo gary ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, I found something to comment from this last email :). >access to on a regular basis. Yes, you can tell the installer >that it should check the architecture. No, you shouldn't be If same installer can be used to install both x86 and PCC binaries depending on which PC you run installation package that would be great. Anyhow I think we can make at least separate PCC installation package when we will have PCC Mac to make it. >that it should check the architecture. No, you shouldn't be >doing that because you should be compiling a PPC binary. Nobody has told me if PCC binary can be build on x86 Mac. If not it will take some time to make PCC version of flasher-3.5 even when it is just rebuilding (at least in theory it should be just rebuilding task). Cheers, //Jarmo >-Original Message- >From: ext Ryan Abel [mailto:rabe...@gmail.com] >Sent: 01 July, 2009 15:37 >To: Tikka Jarmo (Nokia-D/Helsinki) >Cc: maemo-developers@maemo.org; maemo-us...@maemo.org >Subject: Re: Maemo Flasher-3.5 Tool Beta for Fremantle and >Diablo released > >On Wed, Jul 1, 2009 at 2:43 AM, wrote: > >>>One step forward and two steps back. >> >> Happy to see that you considered this Beta release to be at >least one >> step forward (before ending up being one step backward :) >> > >It's hardly every anything else with Nokia. :( > >>> >>>No PPC binary, and the installer will happily chug right >along without >>>telling users that they're installing something they can't even use. >> >> Only x86 and 32-bit support with this beta release. Could >you explain in more detailed your installation problems. E.g. >do you try to install Windows XP or Windows Vista or Mac OS X >10.x or Debian Linux or some other Linux or ... >> > >I don't use Windows, and, by and large, I don't use Linux. > >> Or are you trying to install Mac flasher-3.5 to PPC Mac? I >do not Mac myself well enoug to say if architecture can be >defined to the Mac installation package so that you will get >some sensible error message if you try to install "wrong" >architecture binary. >> > >Yes, because PPC OS X is basically the only thing I have >access to on a regular basis. Yes, you can tell the installer >that it should check the architecture. No, you shouldn't be >doing that because you should be compiling a PPC binary. > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
(Sorry for the terrible quoting. You all knoe exactly how useless an application Modest is. :)) There's absolutely no reason why not. Really, though, why don't we just open source it so we don't have to deal with ANY of this insanity? - Original message - is it possible to do tablet->tablet flashing? (serious question) most of us now have more than one device and since not all of us have linux or windows available (hiya GA), having a native solution would be a possible quicker workaround___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
is it possible to do tablet->tablet flashing? (serious question) most of us now have more than one device and since not all of us have linux or windows available (hiya GA), having a native solution would be a possible quicker workaround gary On Wed, Jul 1, 2009 at 1:36 PM, Ryan Abel wrote: > On Wed, Jul 1, 2009 at 2:43 AM, wrote: > > >>One step forward and two steps back. > > > > Happy to see that you considered this Beta release to be at least one > step forward (before ending up being one step backward :) > > > > It's hardly every anything else with Nokia. :( > > >> > >>No PPC binary, and the installer will happily chug right along > >>without telling users that they're installing something they > >>can't even use. > > > > Only x86 and 32-bit support with this beta release. Could you explain in > more detailed your installation problems. E.g. do you try to install Windows > XP or Windows Vista or Mac OS X 10.x or Debian Linux or some other Linux or > ... > > > > I don't use Windows, and, by and large, I don't use Linux. > > > Or are you trying to install Mac flasher-3.5 to PPC Mac? I do not Mac > myself well enoug to say if architecture can be defined to the Mac > installation package so that you will get some sensible error message if you > try to install "wrong" architecture binary. > > > > Yes, because PPC OS X is basically the only thing I have access to on > a regular basis. Yes, you can tell the installer that it should check > the architecture. No, you shouldn't be doing that because you should > be compiling a PPC binary. > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Wed, Jul 1, 2009 at 2:43 AM, wrote: >>One step forward and two steps back. > > Happy to see that you considered this Beta release to be at least one step > forward (before ending up being one step backward :) > It's hardly every anything else with Nokia. :( >> >>No PPC binary, and the installer will happily chug right along >>without telling users that they're installing something they >>can't even use. > > Only x86 and 32-bit support with this beta release. Could you explain in more > detailed your installation problems. E.g. do you try to install Windows XP or > Windows Vista or Mac OS X 10.x or Debian Linux or some other Linux or ... > I don't use Windows, and, by and large, I don't use Linux. > Or are you trying to install Mac flasher-3.5 to PPC Mac? I do not Mac myself > well enoug to say if architecture can be defined to the Mac installation > package so that you will get some sensible error message if you try to > install "wrong" architecture binary. > Yes, because PPC OS X is basically the only thing I have access to on a regular basis. Yes, you can tell the installer that it should check the architecture. No, you shouldn't be doing that because you should be compiling a PPC binary. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
Hi, >-Original Message- >From: ext Ryan Abel [mailto:rabe...@gmail.com] >Sent: 01 July, 2009 03:05 >Diablo released > >On Tue, Jun 30, 2009 at 8:41 AM, wrote: >> The Maemo Eclipse Integration 2nd Edition project has >released installation packages for Maemo Flasher-3.5 Tool Beta >for Linuxes, Mac OS X and Windows. Maemo Flasher-3.5 tool >supports flashing of N8x0 Diablo devices and coming Fremantle devices. >> > >One step forward and two steps back. Happy to see that you considered this Beta release to be at least one step forward (before ending up being one step backward :) > >No PPC binary, and the installer will happily chug right along >without telling users that they're installing something they >can't even use. Only x86 and 32-bit support with this beta release. Could you explain in more detailed your installation problems. E.g. do you try to install Windows XP or Windows Vista or Mac OS X 10.x or Debian Linux or some other Linux or ... Or are you trying to install Mac flasher-3.5 to PPC Mac? I do not Mac myself well enoug to say if architecture can be defined to the Mac installation package so that you will get some sensible error message if you try to install "wrong" architecture binary. Cheers, //Jarmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Flasher-3.5 Tool Beta for Fremantle and Diablo released
On Tue, Jun 30, 2009 at 8:41 AM, wrote: > The Maemo Eclipse Integration 2nd Edition project has released installation > packages for Maemo Flasher-3.5 Tool Beta for Linuxes, Mac OS X and Windows. > Maemo Flasher-3.5 tool supports flashing of N8x0 Diablo devices and coming > Fremantle devices. > One step forward and two steps back. No PPC binary, and the installer will happily chug right along without telling users that they're installing something they can't even use. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
