Hi Greg,
(Sending again as seems like I had rich-text available by mistake, so
likely my message is rejected)
On Tue, 30 Mar 2021 at 15:40, Greg KH wrote:
>
> On Tue, Mar 30, 2021 at 03:23:10PM +0200, Fawad Lateef wrote:
> > So can I still use kernel-3.4 compiled with gcc-5.5, a
Hi Arnd,
On Mon, 29 Mar 2021 at 22:06, Arnd Bergmann wrote:
>
> On Mon, Mar 29, 2021 at 9:23 PM Fawad Lateef wrote:
> >
> > On Mon, 29 Mar 2021 at 06:57, Greg KH wrote:
> > >
> > > On Sun, Mar 28, 2021 at 10:20:50PM +0200, Fawad Lateef wrote:
> > &
Hi Greg,
On Mon, 29 Mar 2021 at 06:57, Greg KH wrote:
>
> On Sun, Mar 28, 2021 at 10:20:50PM +0200, Fawad Lateef wrote:
> > Hi
> >
> > I am using an Olimex A20 SOM with NAND and due to some binary blob for
> > NAND driver, I am stuck with the sunxi kernel 3.4.xxx
On Sun, 28 Mar 2021 at 22:49, Andy Shevchenko wrote:
>
>
>
> On Sunday, March 28, 2021, Fawad Lateef wrote:
>>
>> Hi
>>
>> I am using an Olimex A20 SOM with NAND and due to some binary blob for
>> NAND driver, I am stuck with the sunxi kernel 3.4.xxx
int: 40008000
Image arch/arm/boot/uImage is ready
-
-- I still can't boot the kernel on the platform. I believe its
because there were lots of warning like above (unused const variables
etc) and might have removed some other code/functions OR macros?
So please suggest what I can do for compiling working kernel-3.4 with gcc-9.
Thanks in advance,
-- Fawad Lateef
573.615558] 3fc0: be9c8950 02018390 0142 0200f368
0002 b6f65e6c 000c
[ 573.623737] 3fe0: be9c8918 b6f967a0 b6e96bc8
[ 573.628795] Code: e597214c e5926000 e3a02000 ee072f9a (e3c66004)
[ 573.634894] ---[ end trace 2247f322516b4181 ]---
#
Thanks in advance,
-- Fawad Lateef
Hi Sebastian,
On 17 May 2017 at 18:02, Sebastian Andrzej Siewior
wrote:
> On 2017-05-17 07:45:39 [-0700], Eric Nelson wrote:
>> Hi Fawad,
> Hi Fawad,
>
>> On 05/17/2017 06:40 AM, Fawad Lateef wrote:
>> > > > I'm not sure about the unhandled page fault,
Hi Eric,
On 17 May 2017 at 16:45, Eric Nelson wrote:
> Hi Fawad,
>
> On 05/17/2017 06:40 AM, Fawad Lateef wrote:
>>
>> On 15 May 2017 at 16:20, Fawad Lateef wrote:
>>>
>>> Hi Eric,
>>> On 15 May 2017 at 16:12, Eric Nelson wrote:
>>>&g
Hi,
On 15 May 2017 at 16:20, Fawad Lateef wrote:
> Hi Eric,
>
>
> On 15 May 2017 at 16:12, Eric Nelson wrote:
>> Hi Fawad,
>>
>>> 发自网易邮箱大师
>>> On 05/15/2017 20:44, Fawad Lateef wrote:
>>>
>>> Hi All,
>>>
>>> I am wo
Hi Eric,
On 15 May 2017 at 16:12, Eric Nelson wrote:
> Hi Fawad,
>
>> 发自网易邮箱大师
>> On 05/15/2017 20:44, Fawad Lateef wrote:
>>
>> Hi All,
>>
>> I am working on custom i.MX6 quad hardware and using RT patches for
>> almost latest stable
Hi Sebastian,
On 15 May 2017 at 15:47, Sebastian Andrzej Siewior
wrote:
> On 2017-05-15 15:09:45 [+0200], Fawad Lateef wrote:
>> Hi,
>>
>> I am talking in general about RT patches. Like downloaded 4.9.20 from
>> kernel.org and applied patch "4.9.20-rt16.patch
Hi,
I am talking in general about RT patches. Like downloaded 4.9.20 from
kernel.org and applied patch "4.9.20-rt16.patch".
Thanks
-- Fawad Lateef
On 15 May 2017 at 14:51, GuJiangfei wrote:
> Which rt patch do you mean?
>
>
> 发自网易邮箱大师
> On 05/15/2017 20:44, Fawad
; As I heard from my other colleagues that RT
patches are not stable for ARM and should be avoided.
Thanks in advance,
-- Fawad Lateef
Hi,
Just as an update (and for future reference for anyone having similar issue):
I got this all this sorted-out. Had to change some dt-binding for
device and it was mostly drivers related changes for hardware
components. Mostly nothing to do with DT.
Thanks
Fawad Lateef
-- Fawad Lateef
On
working.
Thanks
-- Fawad Lateef
On 3 April 2017 at 10:38, Fawad Lateef wrote:
> Hi,
>
> I am facing some issues with device-trees (I am fairly new to them)
> and need some pointers about how to approach below problem:
>
> I got some I.MX6Q based hardware (some custom made whose
ng.
I was assuming that as hardware is still same for both kernel 3.10 and
4.4, so it should work, but seems like something in DT is off for 4.4
kernel.
Any help and suggestions will be good enough for me to look into above issue.
Thanks and regards,
-- Fawad Lateef
21
__longjmp: 64 pc = [c009d11c]
Can someone tell me if there is something wrong in my
porting/implementation __or__ give some hints ? I am attaching the
code in tar.gz (I am doing cross-compilation with embedded tool chain
so please adjust paths in Makefile when compiling)
Thanks
On 11/30/06, Jon Ringle <[EMAIL PROTECTED]> wrote:
Jon Ringle wrote:
> Fawad Lateef wrote:
> > >
> > > Index: linux/arch/arm/mm/init.c
> > >
> ===
> > > --- linux.orig/arch/arm/m
On 11/30/06, Jon Ringle <[EMAIL PROTECTED]> wrote:
Fawad Lateef wrote:
> On 11/30/06, Jon Ringle <[EMAIL PROTECTED]> wrote:
> > Fawad Lateef wrote:
> > > Yes, this can be used if required physical-memory exists
> in the last
> > > part of RAM as
t to some-value if you want to know
later which pages are reserved by you. (can do this reservation work
here: http://lxr.free-electrons.com/source/arch/i386/mm/init.c#605).
CMIIW
--
Fawad Lateef
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
el BIO b/c I m
not sending it to any of my devices
--
Fawad Lateef
-
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/
option of the kernel ..
Waiting for your response and help .....
--
Fawad Lateef
-
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/
ch is 2.4.21-27.ELsmp
I think its now more clear waiting for your resposes !!!
--
Fawad Lateef
-
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/
kmap_atomic successfully returns me the virtual
address but when I use that virtual address like in memcpy the system
hangs .
I m unable to findout why it is happening in RHEL3 kernel Plz
help me in this regard
--
Fawad Lateef
P.S.
My memory reservation and later using that memory
> Hope the interpretation of his somewhat broken english helps :)
>
If ShadowWolf interpretation of Alejandro's question is right and
Alejandro trying to run the LDD2 books examples on 2.6.8-2 then they
won't work on 2.6.x kernel or not even compile
successfully Tha
s depending on the architecture (AFAIK for almost all
supported architectures)
--
Fawad Lateef
-
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
ith KDB
patch applied if u really want to use KDB on Redhat .. And I
think you can also try to apply patch of KDB for 2.4.20 on the Redhat
kenel, that might succeed if redhat havn't changed anything in the
files of 2.4.20 kernel in which KDB patches or make changes .....
--
Faw
any way I can avoid the kernel's bigmem virtual address
> mapping programatically? and still run the program on a bigmem kernel?
>
I think this can be done through specifying GFP_ATOMIC flag in the
memory allocation function, so that it will use ZONE_NORMAL of the
kernel ... (if i m
ll work
> '>'> > I'm booting with my image of kernel 2.4.29. i'm 5 days tryng
> to solve
> '>'> > this problem ...
Upgrading from 2.4.xx kernel series to 2.6.xx series what I found is
that the filesystem must be compiled into the kernel
29 matches
Mail list logo
