at any rate, here is the reason the Blackfin tree has not been merged back
into the mainline tree yet:
http://thread.gmane.org/gmane.linux.uclinux.devel/11456
Let me add that when I used a virtual Box based Linux installation, the
staging dir made the compile process _a_lot_ faster, as (for
Seeing two of my three favorite archs merged is really awesome ! (I did
consider Blackfin for a project, but in the end I did not even test it,
dropping it in favor of NIOS. :( ) (The third arch's distr is not even
out for testing yet and it's main feature is SMP, so a this is bound to
be a di
You don't need an MMU for PIC or XIP.
I do know this. The NIOS gcc3 does not support these. I do hope gcc4 will.
-Michael
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was
I have tried the new nios2mmu gcc4, and I didn't see big issue.
This is GREAT !
(even though I am a little bit afraid of this update).
If there is a possibility to have both compilers on my system and switch
any time when necessary, I'd like to help testing the new stuff. (If
appropriat
glad to see NIOS toolchain port finally getting up to speed.
As I am basing my current project on this, I would be greatly let down,
it the NIOS-uCLinux dist would not prove to be a serious long living
thingy. Regarding the very active mailing list and forum, the 2.6.29
support and updates t
Mike Frysinger wrote:
very long time to do the mirror on my machine. So .. would you please
spare some time to setup blackfin uClinux-dist git mirror?
i'm not sure i understand. there already is one ?
Oh..yes, there is one. Even though it is not shown on the front page.
Silly me..
- Thoma
On Monday 16 February 2009 00:35:35 Thomas Chou wrote:
> Mike Frysinger wrote:
> > the git trees for our main repos are readonly mirrors. some people find
> > it easier to work with git than svn, and it's trivial to provide the
> > mirror on our side, so ...
>
> Even readonly mirror with git will
Mike Frysinger wrote:
the git trees for our main repos are readonly mirrors. some people find it
easier to work with git than svn, and it's trivial to provide the mirror on
our side, so ...
Even readonly mirror with git will be helpful to us. It will take very
very long time to do the mir
On Sunday 15 February 2009 19:56:42 Thomas Chou wrote:
> Mike Frysinger wrote:
> > the logic for merging these two is that NIOS started with the Blackfin
> > tree. if the NIOS guys tried to merge with the main tree, they'd hit the
> > same issues we did (which is where we are already).
>
> We are i
Mike Frysinger wrote:
at any rate, here is the reason the Blackfin tree has not been merged back
into the mainline tree yet:
http://thread.gmane.org/gmane.linux.uclinux.devel/11456
I can acknowledge that the blackfin's staging approach is an easy and
effective way to maintain userspace libra
Mike Frysinger wrote:
the logic for merging these two is that NIOS started with the Blackfin tree.
if the NIOS guys tried to merge with the main tree, they'd hit the same issues
we did (which is where we are already).
We are in the midway. We started with the main uClinux-dist, and pulled
On Friday 13 February 2009 01:29:03 Greg Ungerer wrote:
> Michael Schnell wrote:
> > What is the cause a reunion is not planned ?
>
> Anyone is welcome to send patches to this list for uClinux-dist
> at any time... (But of course they may or may not end up being
> included after consideration).
th
Hi Michael,
Michael Schnell wrote:
Mike Frysinger wrote:
ive tried convincing the uClinux-dist guys to use some of the
methodologies that we've adopted in the Blackfin uClinux dist, but it
doesnt look like it's going to happen, so ive given up :/
Mike, Thomas, Greg.
I always wondered why
On Friday 13 February 2009 09:34:21 Thomas Chou wrote:
> The blackfin has gcc4 already. I have tried the new nios2mmu gcc4, and I
> didn't see big issue.
gcc-4.1 is the stable version now for the Blackfin port. gcc-4.3 is our
experimental version and hopefully will become our stable version over
On Friday 13 February 2009 03:27:36 Michael Schnell wrote:
> > i dont really understand your statement anyways as the current mainline
> > uclinux-dist already supports multiple arches. like arm or coldfire or
> > mips ...
>
> Of course you are right. I just wanted to express that it would seems
>
Michael Schnell wrote:
> (adding support for MMU, so, PIC, and XIP).
You don't need an MMU for PIC or XIP.
-- Jamie
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by u
Michael Schnell wrote:
It does take some effort to do the merge. But we get more when we can
share.
So you _do_ plan a merge ?!?!?!
Yes. You give us this great idea.
The maintainer of blackfin uclinux has kindly granted me to commit to
their svn repo. I will study and proceed to the merge.
T
It does take some effort to do the merge. But we get more when we can
share.
So you _do_ plan a merge ?!?!?!
looks like fun :=)
-Michael
___
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
Thi
i dont really understand your statement anyways as the current mainline
uclinux-dist already supports multiple arches. like arm or coldfire or mips
...
Of course you are right. I just wanted to express that it would seems
funny to me to combine the two of Blackfin and NIOS while others are in
Michael Schnell wrote:
It seems a little bit funny to have a common Blackfin+NIOS git, as these
archs are very different. NIOS will have MMU support some day so this
might be not an easy task.
There is shared lib support on Blackfin even without MMU, via fdpic. As
I am working on Nios2 MMU, I
Mike Frysinger wrote:
we require complete
visibility on our side so we have our own public server hosting the dist via
svn. it is completely up-to-date at all times with the developer and public
accessible.
This is the same reason that we created a public git server for Nios. It
is difficul
On Thursday 12 February 2009 11:40:15 Michael Schnell wrote:
> > as for NIOS/Blackfin, i certainly dont have a problem if the NIOS guys
> > want to merge their work back with ours...
>
> It seems a little bit funny to have a common Blackfin+NIOS git, as these
> archs are very different.
for usersp
as for NIOS/Blackfin, i certainly dont have a problem if the NIOS guys want to
merge their work back with ours...
It seems a little bit funny to have a common Blackfin+NIOS git, as these
archs are very different. NIOS will have MMU support some day so this
might be not an easy task.
-Michael
On Thursday 12 February 2009 03:56:40 Michael Schnell wrote:
> Mike Frysinger wrote:
> > ive tried convincing the uClinux-dist guys to use some of the
> > methodologies that we've adopted in the Blackfin uClinux dist, but it
> > doesnt look like it's going to happen, so ive given up :/
>
> I always
Mike Frysinger wrote:
ive tried convincing the uClinux-dist guys to use some of the methodologies
that we've adopted in the Blackfin uClinux dist, but it doesnt look like it's
going to happen, so ive given up :/
Mike, Thomas, Greg.
I always wondered why there are dedicated "Blackfin" and "N
Mike Frysinger wrote:
ive tried convincing the uClinux-dist guys to use some of the methodologies
that we've adopted in the Blackfin uClinux dist, but it doesnt look like it's
going to happen, so ive given up :/
Hi Mike,
We adopted the excellent works from Blackfin uClinux dist to Nios2
uCl
On Wednesday 11 February 2009 19:26:48 Lars Holowko wrote:
> Thanks a lot Mike,
>
> config.in-to-kconfig.sh did the trick.
great, glad it worked for you
> By the way, I really like to support multiple versions of an app in your
> user tree. I hope the uclinux-dist people will pick it up for their
]
Sent: Tuesday, February 10, 2009 5:03 PM
To: Lars Holowko
Cc: uclinux-dev@uclinux.org
Subject: Re: [uClinux-dev] howto generate Kconfig files from Config.in
for busybox
On Tuesday 10 February 2009 19:42:45 Lars Holowko wrote:
> I digged around a litte bit in uClinux-dist-2008R1.5-RC3. Are
On Tuesday 10 February 2009 19:42:45 Lars Holowko wrote:
> I digged around a litte bit in uClinux-dist-2008R1.5-RC3. Are you
> referring to
> /old/OpenLinux/uClinux-work/user/busybox1110/uclinux-configs/update?
that file isnt from the Blackfin uClinux dist, so no
> Looks like I am on the wrong tr
Subject: Re: [uClinux-dev] howto generate Kconfig files from Config.in
for busybox
On Tuesday 10 February 2009 12:32:47 Lars Holowko wrote:
> I am trying to upgrade the busybox that is part of uClinux-dist to a
> current version.
> The original busybox just comes with Config.in but no Kcon
On Tuesday 10 February 2009 12:32:47 Lars Holowko wrote:
> I am trying to upgrade the busybox that is part of uClinux-dist to a
> current version.
> The original busybox just comes with Config.in but no Kconfig files, the
> latter needed by the uClinux build process.
>
> Since the Kconfig files and
I am trying to upgrade the busybox that is part of uClinux-dist to a
current version.
The original busybox just comes with Config.in but no Kconfig files, the
latter needed by the uClinux build process.
Since the Kconfig files and the Config.in files look almost identical
(mostly USER_BUSYBOX_ pre
32 matches
Mail list logo
