public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Piet Delaney <piet.delaney@tensilica•com>
To: Johannes Weiner <jw@emlix•com>,
	Marc Gauthier <marc@tensilica•com>,
	Chris Zankel <chris@zankel•net>
Cc: Piet Delaney <piet.delaney@gmail•com>,
	Piet Delaney <pdelaney@tensilica•com>, Cord Seele <cs@emlix•com>,
	Oskar Schirmer <os@emlix•com>, Daniel Gloeckner <dg@emlix•com>,
	Piet Delaney <piet@tensilica•com>,
	Maxim Grigoriev <maxim@tensilica•com>,
	Dan Nicolaescu <dann@tensilica•com>,
	Bill Huffman <huffman@tensilica•com>,
	Ross Morley <ross@tensilica•com>,
	Chris Jones <cjones@tensilica•com>,
	linux-xtensa@linux-xtensa•org, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, Dror Maydan <maydan@tensilica•com>
Subject: Re: [patch 0/8] xtensa: s6000 & s6105 - Git Repo Pulled; will try to merge early next week and get back to ya.
Date: Sat, 04 Apr 2009 04:01:23 -0700	[thread overview]
Message-ID: <49D73E03.9040702@tensilica.com> (raw)
In-Reply-To: <20090327141226.GA26597@emlix.com>

Johannes Weiner wrote:

>> What's you proposal?
> 
> Sounds terrific.  I wish you had told us this plan before, that would
> have saved us quite some discussion ;)
> 
> So please let us know where to find the merged tree when it's ready.
> We will test it on our S6000 board and look over your work.

I resolved the problems with the merge this evening and posted a
copy here and at kernel.org:

     git+ssh://git.linux-xtensa.org/git/kernel/xtensa-2.6.29-smp

     git://git.kernel.org/pub/scm/linux/kernel/git/piet/xtensa-2.6.29-smp.git

I have two SMP FPGA systems testing the merge, one with cache aliasing, the other
without. Both have been up now running NTP as a stress test for about two hours
without any problems. Earlier this evening I did have one problem when it was just
sitting idle; looked like a problem I had before and fixed.

I had one problem I've not worked around for now. In vmlinux.lds.in.S you added a
#include of <platform/hardware.h> put this causes compile problems for the LX60
platform. You added it to define KERNELOFFSET where as I was bringing it from
asm/core.h which caused less problems. <platform/hardware.h> seems reasonable,
haven't got a clean solution for the asm macro problem yet for LX60 platform.

Could you try this on your S6000 boards and look over our work. I'll
try using xt-gdb and ocd with the Stretch board. I likely have a few
minor tweaks in the Kconfig for _S6000 for selecting optimal defaults.


-piet







	

           reply	other threads:[~2009-04-04 11:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20090327141226.GA26597@emlix.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D73E03.9040702@tensilica.com \
    --to=piet.delaney@tensilica$(echo .)com \
    --cc=chris@zankel$(echo .)net \
    --cc=cjones@tensilica$(echo .)com \
    --cc=cs@emlix$(echo .)com \
    --cc=dann@tensilica$(echo .)com \
    --cc=dg@emlix$(echo .)com \
    --cc=huffman@tensilica$(echo .)com \
    --cc=jw@emlix$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-xtensa@linux-xtensa$(echo .)org \
    --cc=marc@tensilica$(echo .)com \
    --cc=maxim@tensilica$(echo .)com \
    --cc=maydan@tensilica$(echo .)com \
    --cc=os@emlix$(echo .)com \
    --cc=pdelaney@tensilica$(echo .)com \
    --cc=piet.delaney@gmail$(echo .)com \
    --cc=piet@tensilica$(echo .)com \
    --cc=ross@tensilica$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox