On Thu, 29 Nov 2007 21:03:49 +0100
Clemens Koller <[EMAIL PROTECTED]> wrote:
> >> My guess is that the new rtc-lib's RTC_DRV_DS1307 support is still broken
> >> and it also breaks the deprecated SENSORS_DS1337. :-(
>
> One more update:
> I am back to mainline (linus' .git) on 2.6.24-rc3-g09f345da
Hi There!
> Clemens Koller <[EMAIL PROTECTED]> wrote:
>> Well, as already mentioned, I have problems to get my DS1337 RTC on I2C
>> on my MPC8540(ads like) PowerPC working properly on
>> latest 2.6.24-rc2-ge6a5c27f kernels. A paulus.git 2.6.21-rc5-g9a5ee4cc
>> as well as a 2.6.22-rc6-gb75ae860 is
> From: robert lazarski
> Sent: Thursday, November 29, 2007 7:00 AM
> Subject: Re: The question about the high memory support on MPC8360?
> I also have a requirement to use more than 768MB and 0x3000. I
> have other problems at the moment, so I haven't tested this completely
> yet. My limited u
Robert lazarski wrote:
> On Nov 29, 2007 2:29 AM, vijay baskar <[EMAIL PROTECTED]> wrote:
> >
> > How to make the linux find the total 2GB memory?
> >
> > Hi Friend,
> >
> > I hope u had tracked the conversion that has been going on. The max mem
> > that the kernel can show is only 768 MB
On Nov 29, 2007 2:29 AM, vijay baskar <[EMAIL PROTECTED]> wrote:
>
> How to make the linux find the total 2GB memory?
>
>
> Hi Friend,
>
> I hope u had tracked the conversion that has been going on. The max mem
> that the kernel can show is only 768 MB because only that of memory is
> dir
David H. Lynch Jr. wrote:
> I had a similar problem. In my instance it turned out that I was
> inadvertently using the physical address of my uart as the output address.
> This worked during boot becasue there was a 1:1 physical-logical entry
> stuffed into the MMU. But since Linux did nto know ab
Hello, Raul!
[EMAIL PROTECTED] schrieb:
> I am trying to use some devices on i2c protocol, one of them is the DS1337
> RTC, but I don't know too much about how.
> I am using the Linux kernel 2.6.15 and a mpc866 processor.
I don't remember too much about these old kernels.
And, please notice, t
I had a similar problem. In my instance it turned out that I was
inadvertently using the physical address of my uart as the output address.
This worked during boot becasue there was a 1:1 physical-logical entry
stuffed into the MMU. But since Linux did nto know about it, as soon as
the VM system de
Hello all,
I am trying to use some devices on i2c protocol, one of them is the DS1337
RTC, but I don't know too much about how.
I am using the Linux kernel 2.6.15 and a mpc866 processor. I've seen there
is a cpm i2c interface for these processors (for a rpx board). However the
corresponding code (
Hello, Allessandro!
Alessandro Zummo schrieb:
> On Wed, 28 Nov 2007 19:25:00 +0100
> Clemens Koller <[EMAIL PROTECTED]> wrote:
>
>> Well, as already mentioned, I have problems to get my DS1337 RTC on I2C
>> on my MPC8540(ads like) PowerPC working properly on
>> latest 2.6.24-rc2-ge6a5c27f ke
John Williams wrote:
>
> I'm not sure I agree, here, given that most people building MicroBlaze
> systems are doing so with uClinux-dist (or PetaLinux), you can do a
> full rebuilt, kernel libs apps, in a couple of minutes. Much shorter
> than sythnesis and P&R, that's for sure (and runtime is line
Hi Dell (???),
On Thursday 29 November 2007, Dell Query wrote:
> 1. I used the 0x1c0002000 offset because I was referring to the first reply
> that I received. Now, I used the address 0x1c0002000 and tried to read from
> it. I retrieved 0x0f01c087. May I know what does this mean? How does this
> d
Hi Stefan,
1. I used the 0x1c0002000 offset because I was referring to the first reply
that I received. Now, I used the address 0x1c0002000 and tried to read from it.
I retrieved 0x0f01c087. May I know what does this mean? How does this data
relate to Board ID?
2. Referring back to "Embedded P
13 matches
Mail list logo
