the padding and APIC support and everything seems to be fine,
but _VERY_ slow. Is this change ok locally? Has it been addressed
in a patch?
regards,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL P
>>>>> "WJP" == Bill Pringlemeir <[EMAIL PROTECTED]> writes:
[snip]
WJP> I have the 2.4.4 distribution from kernel.org.
WJP> "http://www.kernel.org/pub/linux/kernel/v2.4/";
WJP> I have a Mandrake system and selected the AMD processors and
>>>> On 05.18 Bill Pringlemeir wrote:
>> Why don't the build scripts run a dummy file to determine where
>> the floating point registers should be placed?
>>
>> ... const int value = offsetof(struct task_struct,
>> thread.i387.fxsave)
ligned (16)));
union i387_unioni387;
This is a much simpler way of achieving what I was trying to explain
previously. I think that this syntax has been in the GCC extensions
for some time.
regards,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscrib
nfamiliar with how I should use
ksyms to decode this for people... Are these physical addresses or
virtual? I guess I should look at the source... Anyways, the script
does *work* but not as advertised ;-)
fwiw,
Bill Pringlemeir.
inting eip:
c01caa92
*pde =
Oops: 0002
CPU:0
EIP:0
> "John" == John Lenton <[EMAIL PROTECTED]> writes:
John> I found to my dismay that it's extremely easy to crash 2.4.4 if
John> it has a Live! in it. I have no way of getting at the oops, but
John> somebody out there probably has both this soundcard and a
John> serial console (or somethin
rrupts and you do not have any `cycles' in the
function call hierarchies.
hth,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
>>>>> Bill Pringlemeir <[EMAIL PROTECTED]> writes:
> There was a discussion on comp.arch.embedded about bounded stack
> use. It is fairly easy to calculate the stack usage for call
> trees, but much more difficult for `DAGs'. Ie, a recursive
>
> "Peter" == Peter Svensson <[EMAIL PROTECTED]> writes:
Peter> Kelvin (decikelvin?) is probably a good unit to use in the
Peter> kernel. If you want something else you convert it in the
Peter> programs you use to interact with the kernel. This is a
Peter> usespace issue, I think.
How abo
er, no one knows the accuracy of any future
temperature sensors so why not accommodate the possibility. Certainly
some band gap semis can give a pretty good measurement if you have
good coupling. If the temperature sensor was built into the CPU, you
might actually have accuracy!
regards,
Bill Pringleme
y,
but at least I won't have went through the effort. Now that I have
pointed that out, the will probably irk people even more...
regards,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED
y other small oddities, post that diff. If no one
complains, etc I can ask the maintainer. Of course I will test it
myself as well.
regards,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
haven't
the faintest clue about PC controllers.
Perhaps when I am feeling brave again, I will return to try additional
memory.
hth,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo in
test for SDRAM cache lines. Single
beat SDRAM read/writes are less stressful than BURSTS. It is typical
for single beats read/write to work while bursts fail as four 32 bit
values are written and read in quick succession. The `algorithm'
description on the web page doesn't seem to t
discussed before. Unlike disk encryption, I
couldn't find a reference to this topic, but maybe my search was using
the wrong nomenclature. The susinct question would be is this worth
implementing?
tia,
Bill Pringlemeir.
-
To unsubscribe from this list: send the line "unsubscribe linux-ke
On 26 Aug 2015, computersforpe...@gmail.com wrote:
> On Wed, Aug 26, 2015 at 10:57:38AM -0700, Stefan Agner wrote:
>> When printing the ECC error count on ECC fail when reading an erased
>> NAND flash, the numbers of bit flips (stuck at zero) seem to widely
>> correlate with the number returned b
On 9 Jun 2015, sebast...@breakpoint.cc wrote:
> On 2015-06-06 11:53:31 [+0200], Stefan Agner wrote:
>> +static const struct of_device_id vf610_nfc_dt_ids[] = {
>> +{ .compatible = "fsl,vf610-nfc" },
>> +{ .compatible = "fsl,mpc5125-nfc" },
> I advise against a "fsl,mpc5125-nfc" binding.
ruction is used. If not, then a
generic version is used as you have coded. The PowerPC (another
possible future ARCH for QorIQ/Layerscape SOC?) always has inline
assembler macros.
So,
+ #include
...
+ #define FTM_SWAP32(b, v) (b ? __swab32(v) : v)
might be better.
Suggested-by: Bill Pringlemeir
Thanks,
Bill Pringlemeir.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 24 Sep 2014, ste...@agner.ch wrote:
> This patchset came out of need for a clocksource which supports
> shutdown. In the first version I proposed to just replace the current
> clocksource with the ARM Global Timer and even proposed to remove the
> PIT clocksource driver. But Bill
ternal
muxing is used or not needed, then 'control=false' can be set (or
whatever good DT terminology)? Then the 'GPIO_CONTROL' check would be
in the 'vf610_gpio_direction_input()' functions. The 'pinctrl'
functions are currently compiled to stubs if that
gt; imx_pmx_gpio_request_enable (e.g. drive strenght etc), rather then
>>> only mux the pad to to GPIO...
>>> What do you think?
> Am 2014-09-25 18:43, schrieb Bill Pringlemeir:
>> The muxing must have been done, that is correct. However, this could
>> be by a boot
On 8 Jul 2015, shawn...@kernel.org wrote:
> On Fri, Jun 19, 2015 at 12:58:37AM +0200, Stefan Agner wrote:
>> Enable the NAND Flash Controller driver which is part of the Vybrid
>> SoC by default.
>>
>> Signed-off-by: Stefan Agner
>> ---
>> arch/arm/mach-imx/Kconfig | 1 +
>> 1 file changed, 1 ins
On 25 Aug 2015, computersforpe...@gmail.com wrote:
> Sorry, I realized a potential issue here.
> On Mon, Aug 03, 2015 at 11:27:28AM +0200, Stefan Agner wrote:
>> Signed-off-by: Bill Pringlemeir
>> Acked-by: Shawn Guo
>> Reviewed-by: Brian Norris
>&g
a consistent layout of the includes would be valuable.
Definitely, the repeated information in the DT is bad. Is there an
unwritten standard? I think it would be useful to point out an example
that should be the prototype? Do we have one? Ie, some SOC family that
we would like as an example?
On 9 Mar 2015, ste...@agner.ch wrote:
> Signed-off-by: Bill Pringlemeir
> Signed-off-by: Stefan Agner
> ---
> .../devicetree/bindings/mtd/vf610-nfc.txt | 39 ++
> 1 file changed, 39 insertions(+) create mode 100644
> Documentation/devicetree/bindings
k/coldfire
(patched) kernels and I wanted it to be useful for them. However, we
could probably remove the 'platform support'. Other people are using
this on PPC platforms and they will also have dt/of.
Currently the platform control has no way to 'pass data', so the driver
only works with whatever defaults it has (or that is my belief). For
instance, those OpenWRT kernels have a 'machine file' which will set the
'clock-frequency' and other parameters. We could remove the platform
support completely if it is misleading. I guess the KConfig would need
a 'depends on CONFIG_OF'.
Thanks for the review,
Bill Pringlemeir.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
26 matches
Mail list logo
