From: kevin diggs <hidden> Date: 2011-03-11 18:04:20
Hi,
While trying to figure out why the MESH SCSI controller will not work
with the 4.3.5 compiler but will work when compiled with 4.1.2, I
noticed some ... unfortunate behavior from the 4.3.5 compiler. Before
I try to see if I can fix it (i.e. the compiler), it would be nice to
see if the "issue" still exists.
Is there any chance someone with a compiler newer than 4.3.5 would be
willing to get me -S output from a mesh compile (preferably not a
module unless it does not make any difference) for 2.6.36. Using:
head -1 <top>/drivers/scsi/.mesh.o.cmd
you can get a command line which can then be edited to get a script to
do a -S compile (watch out for the '\#' in KBUILD_STR(s)).
Thanks!
kevin
Is there any chance someone with a compiler newer than 4.3.5 would be
willing to get me -S output from a mesh compile (preferably not a
module unless it does not make any difference) for 2.6.36. Using:
head -1 <top>/drivers/scsi/.mesh.o.cmd
you can get a command line which can then be edited to get a script to
do a -S compile (watch out for the '\#' in KBUILD_STR(s)).
make drivers/scsi/mesh.s
File sent separately, I doubt the list wants to see it.
Segher
From: kevin diggs <hidden> Date: 2011-03-12 01:43:15
Hi,
Good to know. I just tried this on an x86 laptop. It was NOT happy!
And, obviously, I am not using a mesh SCSI controller on my Toshiba
A75.
And thanks again for your time!
kevin
On Fri, Mar 11, 2011 at 7:39 PM, Segher Boessenkool
[off-list ref] wrote:
quoted
quoted
make drivers/scsi/mesh.s
??? I thought I have tried this in the past and it did not work? The
make <path>/<file>.s thing?
Thanks for the tip!
You need to have the driver in your kernel config, or things will
go weird.
Segher