* [U-Boot] x86 cleanup patches
From: Wolfgang Denk @ 2011-11-06 19:09 UTC (permalink / raw)
To: u-boot
In-Reply-To: <4EB67A6E.2090902@gmail.com>
Dear Graeme Russ,
In message <4EB67A6E.2090902@gmail.com> you wrote:
>
> I have two x86 tidy-up patch series that I intend to apply in the next 2-3
> weeks to a 'next' branch on the x86 repo. Being 'next', these patches are
> intended for the current merge window which closes on December 12
You confuse me.
Currently the merge window is closed. The next release is scheduled
for December 12. ONly then, the _next_ merge window will open.
> Please be aware that the latest series (checkpatch cleanup) is designed to
> be applied first, but it was actually created _after_ the 'Various x86
> cleanups' series and hence, there is a wee little bit of incompatibility
> between the two (and silly me should have called the latest one v0 as
> well...). The conflicts aren't so bad - I already have them resolved but
> the second series is not checkpatch clean yet. Before I apply this series
> to 'next' I will be posting a unified patch set in the next week or so - It
> will be a 12 part series which will line up 1-to-1 so I'll be setting the
> in-reply-to to thread from the current patches. In the meantime, please:
This being mostly cleanup, and we still being relatively early in the
stabilization phase, I would also accept this stuff now.
> 1) Have a look at the two independent series and let me know if there is
> any glaring issues I need to address
I will, time permitting.
> 2) Let me know if you need more than two weeks
?
> 3) Be prepared to rebase any current x86 patches against 'next' in three
> weeks time (unless otherwise informed)
?
> Gabe, going by this schedule, there will be a good two weeks between the
> x86 cleanup hitting 'next' and the merge window closing - I think this
Which merge window are you talking about?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
GUIs are virtually useless. Learn tools. They're configurable,
scriptable, automatable, cron-able, interoperable, etc. We don't need
no brain-dead winslurping monolithic claptrap.
-- Tom Christiansen in 371140df at csnews
^ permalink raw reply
* Re: [PULL] Add support for Texas Instruments C6X architecture
From: Linus Torvalds @ 2011-11-06 19:07 UTC (permalink / raw)
To: Mark Salter; +Cc: linux-kernel, Arnd Bergmann
In-Reply-To: <1320593057.14081.107.camel@deneb.redhat.com>
On Sun, Nov 6, 2011 at 7:24 AM, Mark Salter <msalter@redhat.com> wrote:
>
> I think the best counter argument is that it leads to paddr != vaddr
> in the case of NOMMU with a non-zero memory base. My view is that in
> all NOMMU cases, physical and virtual addresses should be the same.
> Otherwise, you end up breaking drivers which need to pass physical
> addresses to devices.
That's a totally insane argument.
Quite frankly, if this is what things rest on, I really *really* don't
want to take the change.
It's a broken argument. It's stupid.
AND IT ISN'T EVEN TRUE!
The "device view" of memory need not at all be the same as the CPU
view, and that has absolutely nothing to do with CPU MMU remapping.
There is a very good reason why we consider "virtual" != "physical" !=
"bus dma" address, and it's very simple: they aren't the same things
at all.
I think some 32-bit PowerPC chips, for example, will see "physical
address zero" at zero (for the CPU), but the devices on the PCI bus
consider "address zero" to be the PCI memory mapping. The devices see
physical RAM starting at DMA address 0x80000000, while for the CPU,
thats's where PCI MMIO lives.
Dammit, if a driver needs to pass a DMA address, that driver will
absolutely need to translate virtual (*or* physical) addresses to
"bus" addresses. End of story. Trying to even *imply* anything else is
pure and utter garbage, and saying that virtual addresses have to
match physical ones in order to not break drivers is drivel that I am
not at all interested in hearing.
Of course, reality is even more complicated than that, and the "bus
address" may well depend on the particular bus the device lives on. So
these days we don't even really encourage the simple mappings like
"virt_to_bus()" any more, we use bus-specific DMA helper functions to
allocate and map the DMA addresses
I suggest you sit down with some other embedded developers and think
about it, and if you all can come up with a good argument for why
things should work a particular way, we can do it that way (regardless
of what that way is). The PowerPC people have seen all the craziness
there is, they would be good to talk to. They also tend to have some
of the more complicated setups.
I'm not saying that <asm-generic/page.h> should necessarily be the
most generic and complicated model out there (perhaps the reverse -
complicated models can use their own arch-specific ones), but I do
think that it should *not* be based on broken assumptions like "dma ==
physical == virtual" address, and encourage a model where simple
architectures don't need any mapping at all. Because that is NOT TRUE,
and has nothing to do with MMU or not-MMU.
So right now I'm not going to merge this, especially when the
arguments for the change are not ones I consider
to be even remotely valid.
And my gut feel is that architectures should *aim* at "pfn's" starting
basically at zero. I'm not saying it's a requirement, and I can be
convinced otherwise, but you should strive to think of pfn's as
"physical page indexes". If memory fundamentally starts at some
specific offset, and there cannot be RAM below that offset, then my
gut feel is that the right define for virt_to_pfn() on such an
architecture would be to subtract the offset and then shift by the
page size.
(Btw, that's not what PPC32 does - it has some "MEMORY_START" logic
which is actually fairly complex. Maybe they had reasons for their
choice, and maybe they are historical. But I want more discussion
about what the "asm-generic/page.h" implementation should be, and I
think the C6x changes are counter-intuitive)
Linus
^ permalink raw reply
* Re: [PATCH] beaglebone-getting-started: Update Mac driver
From: Koen Kooi @ 2011-11-06 19:06 UTC (permalink / raw)
To: Jason Kridner; +Cc: meta-ti
In-Reply-To: <1320579644-14051-1-git-send-email-jdk@ti.com>
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
Op 6 nov. 2011, om 12:40 heeft Jason Kridner het volgende geschreven:
> This still isn't complete, but I wanted to push the latest Mac drivers
> to be certain they are in the next build.
Applied, thanks! You should see a new build appear in the usual location(s) in ±3 hours from now.
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
^ permalink raw reply
* Re: [Xenomai-help] Xenomai 2.6.0 - kernel seg faults on AT91
From: Gilles Chanteperdrix @ 2011-11-06 19:03 UTC (permalink / raw)
To: at91_enthus; +Cc: xenomai
In-Reply-To: <4EB6D941.7080206@domain.hid>
On 11/06/2011 08:00 PM, at91_enthus wrote:
> On 11/06/2011 12:32 PM, Gilles Chanteperdrix wrote:
>> On 11/06/2011 07:25 PM, at91_enthus wrote:
>>> On 11/06/2011 12:10 PM, at91_enthus wrote:
>>>> On 11/06/2011 12:01 PM, Gilles Chanteperdrix wrote:
>>>>> On 11/06/2011 06:56 PM, at91_enthus wrote:
>>>>>> Hi.
>>>>>>
>>>>>> I gave Xenomai 2.6.0 a try and installed a newly patched kernel on my
>>>>>> AT91SAM9G20 board.
>>>>>>
>>>>>> Here is my setup:
>>>>>>
>>>>>> proc: AT91SAM9G20
>>>>>> kernel: 2.6.35.9
>>>>>> OS: embedded Debian Squeeze
>>>>>>
>>>>>> The board boots fine up to stage 2 (user terminal). Sometimes, I am able
>>>>>> to get a login terminal, despite seg fault messages.
>>>>>>
>>>>>> A similar behavior occurs in a Xenomai capable 2.6.37 kernel, only
>>>>>> without the fault messages. In this case the board simply freezes.
>>>>>>
>>>>>> I included the files (.config and fault messages) in the attachments.
>>>>>>
>>>>> You enabled CONFIG_FCSE_GUARANTEED, I do not think Debian squeeze can
>>>>> boot with that, you need a real embedded filesystem, or use
>>>>> CONFIG_FCSE_BEST_EFFORT.
>>>>>
>>>>>
>>>> Since I've started looking in to Xenomai, I have been using FCSE
>>>> "guaranteed" and "best efort" along with both Debian Squeeze and Lenny
>>>> (Xenomai 2.5 series) without any issues.
>>>>
>>>> I'll change the FCSE setting to see if I get a different behavior.
>>>>
>>>> Regards.
>>> I put the results for CONFIG_FCSE_BEST_EFFORT in the attachment.
>> Unusable. To make it usable, the following options are lacking:
>> CONFIG_FCSE_MESSAGES
>
>> CONFIG_FRAME_POINTER
>
> I couldn't find this option.
You need to disable STACK_UNWIND. Without it, some stack traces are
unreadable such as the one you keep sending.
--
Gilles.
^ permalink raw reply
* Re: [Xenomai-help] Xenomai 2.6.0 - kernel seg faults on AT91
From: at91_enthus @ 2011-11-06 19:00 UTC (permalink / raw)
To: xenomai
In-Reply-To: <4EB6D2A4.2020102@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]
On 11/06/2011 12:32 PM, Gilles Chanteperdrix wrote:
> On 11/06/2011 07:25 PM, at91_enthus wrote:
>> On 11/06/2011 12:10 PM, at91_enthus wrote:
>>> On 11/06/2011 12:01 PM, Gilles Chanteperdrix wrote:
>>>> On 11/06/2011 06:56 PM, at91_enthus wrote:
>>>>> Hi.
>>>>>
>>>>> I gave Xenomai 2.6.0 a try and installed a newly patched kernel on my
>>>>> AT91SAM9G20 board.
>>>>>
>>>>> Here is my setup:
>>>>>
>>>>> proc: AT91SAM9G20
>>>>> kernel: 2.6.35.9
>>>>> OS: embedded Debian Squeeze
>>>>>
>>>>> The board boots fine up to stage 2 (user terminal). Sometimes, I am able
>>>>> to get a login terminal, despite seg fault messages.
>>>>>
>>>>> A similar behavior occurs in a Xenomai capable 2.6.37 kernel, only
>>>>> without the fault messages. In this case the board simply freezes.
>>>>>
>>>>> I included the files (.config and fault messages) in the attachments.
>>>>>
>>>> You enabled CONFIG_FCSE_GUARANTEED, I do not think Debian squeeze can
>>>> boot with that, you need a real embedded filesystem, or use
>>>> CONFIG_FCSE_BEST_EFFORT.
>>>>
>>>>
>>> Since I've started looking in to Xenomai, I have been using FCSE
>>> "guaranteed" and "best efort" along with both Debian Squeeze and Lenny
>>> (Xenomai 2.5 series) without any issues.
>>>
>>> I'll change the FCSE setting to see if I get a different behavior.
>>>
>>> Regards.
>> I put the results for CONFIG_FCSE_BEST_EFFORT in the attachment.
> Unusable. To make it usable, the following options are lacking:
> CONFIG_FCSE_MESSAGES
> CONFIG_FRAME_POINTER
I couldn't find this option.
> CONFIG_DEBUG_USER
> CONFIG_DEBUG_ERRORS
>
> And add debug_user=29 on the command line.
>
The results were attached.
[-- Attachment #2: messages-DEBUGs-set --]
[-- Type: text/plain, Size: 15178 bytes --]
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.35.9-xenomai (user@hive64) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #5 Sun Nov 6 12:43:51 CST 2011
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00057177
CPU: VIVT data cache, VIVT instruction cache
Machine: Micromint Electrum 100
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait lpj=98304 noswap debug_user=29
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61768k/61768k available, 3768k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc4800000 - 0xfee00000 ( 934 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0020000 ( 96 kB)
.text : 0xc0020000 - 0xc02c8000 (2720 kB)
.data : 0xc02de000 - 0xc02f7f60 ( 104 kB)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:192
AT91: 96 gpio irqs in 3 banks
AT91 I-pipe timer: div: 128, freq: 1.032000 MHz, wrap: 63.503875 ms
I-pipe, 1.032 MHz clocksource
I-pipe 1.18-03: pipeline enabled.
Console: colour dummy device 80x30
Calibrating delay loop (skipped) preset value.. 196.60 BogoMIPS (lpj=98304)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after user reset
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource ipipe_tsc
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
I-pipe: Domain Xenomai registered.
Xenomai: hal/arm started.
Xenomai: scheduling class idle registered.
Xenomai: scheduling class rt registered.
Xenomai: real-time nucleus v2.6.0 (Movin' On) loaded.
Xenomai: debug mode enabled.
Xenomai: starting native API services.
Xenomai: starting POSIX services.
Xenomai: starting RTDM services.
msgmni has been set to 120
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
console [ttyS0] enabled
atmel_usart.1: ttyS1 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffc8000 (irq 12)
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:21:a3:00:02:89)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
TCP cubic registered
NET: Registered protocol family 17
rtc-at91sam9 at91_rtt.0: setting system clock to 2011-11-06 13:44:14 UTC (1320587054)
Waiting for root device /dev/mmcblk0p2...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address 3375
mmcblk0: mmc0:3375 SD02G 1.83 GiB
mmcblk0: p1 p2 p3 p4
EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext2 filesystem) on device 179:2.
Freeing init memory: 96K
INIT: version 2.88 booting
INIT: Entering runlevel: 2
Unable to handle kernel paging request at virtual address c4000000
fcse pid: 5, 0x0a000000
pgd = c3db0000
[c4000000] *pgd=00000000
Internal error: Oops: 805 [#1]
last sysfs file:
Modules linked in:
CPU: 0 Not tainted (2.6.35.9-xenomai #5)
PC is at __memzero+0x30/0x80
LR is at 0x0
pc : [<c0162c50>] lr : [<00000000>] psr: 20000013
sp : c3dcbec8 ip : 00000000 fp : 0001c50c
r10: 00000000 r9 : c3dca000 r8 : 7ffff000
r7 : 00028260 r6 : c3dcbf1c r5 : c3dcbee4 r4 : 00000000
r3 : 00000000 r2 : 00000000 r1 : 7fdcaee0 r0 : c3fffff4
Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 0005717f Table: 23db0000 DAC: 00000015
Process rc.local (pid: 435, stack limit = 0xc3dca270)
Stack: (0xc3dcbec8 to 0xc3dcc000)
bec0: c0238374 7ffde260 7ffff000 c007fd70 c02ebd38 c007fda0
bee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfa0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfe0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[<c0162c50>] (__memzero+0x30/0x80) from [<7ffde260>] (0x7ffde260)
Code: e2511040 a8a0500c a8a0500c a8a0500c (a8a0500c)
---[ end trace ab8cbf29a9038c74 ]---
Unable to handle kernel NULL pointer dereference at virtual address 00000000
fcse pid: 0, 0x00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 17 [#2]
last sysfs file:
Modules linked in:
CPU: 0 Tainted: G D (2.6.35.9-xenomai #5)
PC is at unlink_anon_vmas+0x10/0xb0
LR is at free_pgtables+0x58/0xa4
pc : [<c00c9670>] lr : [<c00c2ae8>] psr: 80000013
sp : c3dcbcc0 ip : c0303b40 fp : 00000001
r10: 00001000 r9 : c02e233c r8 : 00100100
r7 : 00800000 r6 : c3dd2f98 r5 : c3dd2fd0 r4 : 00000000
r3 : 00a1d000 r2 : 00000000 r1 : 00000000 r0 : c3dd2f98
Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 0005717f Table: 23db0000 DAC: 00000015
Process rc.local (pid: 435, stack limit = 0xc3dca270)
Stack: (0xc3dcbcc0 to 0xc3dcc000)
bcc0: 00000000 c3da96a8 c3dd2f98 00800000 00000000 c02e233c 00001000 c00c2ae8
bce0: 00800000 00000000 00000120 00000000 c3d78ba0 c3da9910 00000000 20000013
bd00: c029389a c00c4770 c3dcbd10 00000000 00000024 c02e233c c3d78ba0 c3d78ba0
bd20: c3cd3a00 c3d78bd4 00000805 c0038ce4 00000000 c003ca50 c3cd3a00 c3cd3a00
bd40: c3dcbe80 0000000b c3cd3a00 c3cd3a00 c3dcbe80 c003e1d4 c3cd3a00 c3dca000
bd60: c3dcbe80 00000000 c3cd3a00 c3dca000 c3dcbe80 00000805 20000013 c029389a
bd80: 0001c50c c0024a08 c3dca270 0000000b 00000805 c4000000 c3dcbe80 c3d78ba0
bda0: 00000805 00000000 00000000 c00280e8 23db0000 c3dcbe80 c4000000 00000805
bdc0: c4000000 c00285a8 00000001 c02e20c8 c3dcbeb4 00000805 c3dcbe80 c00202d0
bde0: c3dcbde0 00000100 c3dca000 00000024 00000001 00000009 c0301188 0000000a
be00: 00000000 c0067144 00000000 c0040178 c02e6b70 00000011 00000000 00000011
be20: 00000000 00000000 00000002 c0303b40 00000011 c00400c8 00000011 c0020074
be40: c0305860 00000011 00000014 c0068180 c02eb9c0 c3dcbe80 fefff000 00000011
be60: 00028260 7ffff000 ffffffff c3dcbeb4 c3dcbf1c 00028260 7ffff000 c0020b3c
be80: c3fffff4 7fdcaee0 00000000 00000000 00000000 c3dcbee4 c3dcbf1c 00028260
bea0: 7ffff000 c3dca000 00000000 0001c50c 00000000 c3dcbec8 00000000 c0162c50
bec0: 20000013 ffffffff c0238374 7ffde260 7ffff000 c007fd70 c02ebd38 c007fda0
bee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bf80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfa0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
bfe0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[<c00c9670>] (unlink_anon_vmas+0x10/0xb0) from [<c00c2ae8>] (free_pgtables+0x58/0xa4)
[<c00c2ae8>] (free_pgtables+0x58/0xa4) from [<c00c4770>] (exit_mmap+0x110/0x184)
[<c00c4770>] (exit_mmap+0x110/0x184) from [<c0038ce4>] (mmput+0x44/0x130)
[<c0038ce4>] (mmput+0x44/0x130) from [<c003ca50>] (exit_mm+0x114/0x120)
[<c003ca50>] (exit_mm+0x114/0x120) from [<c003e1d4>] (do_exit+0x170/0x610)
[<c003e1d4>] (do_exit+0x170/0x610) from [<c0024a08>] (die+0x1a0/0x1d4)
[<c0024a08>] (die+0x1a0/0x1d4) from [<c00280e8>] (__do_kernel_fault+0x64/0x84)
[<c00280e8>] (__do_kernel_fault+0x64/0x84) from [<c00285a8>] (do_translation_fault+0x114/0x130)
[<c00285a8>] (do_translation_fault+0x114/0x130) from [<c00202d0>] (do_DataAbort+0x34/0x120)
[<c00202d0>] (do_DataAbort+0x34/0x120) from [<c0020b3c>] (__dabt_svc+0x5c/0x80)
Exception stack(0xc3dcbe80 to 0xc3dcbec8)
be80: c3fffff4 7fdcaee0 00000000 00000000 00000000 c3dcbee4 c3dcbf1c 00028260
bea0: 7ffff000 c3dca000 00000000 0001c50c 00000000 c3dcbec8 00000000 c0162c50
bec0: 20000013 ffffffff
[<c0020b3c>] (__dabt_svc+0x5c/0x80) from [<c0162c50>] (__memzero+0x30/0x80)
[<c0162c50>] (__memzero+0x30/0x80) from [<7ffde260>] (0x7ffde260)
Code: e92d47f0 e1a05000 e5b54038 e59f808c (e4143008)
---[ end trace ab8cbf29a9038c75 ]---
Fixing recursive fault but reboot is needed!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
fcse pid: 0, 0x00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 80000005 [#3]
last sysfs file:
Modules linked in:
CPU: 0 Tainted: G D (2.6.35.9-xenomai #5)
PC is at 0x0
LR is at __rcu_process_callbacks+0x320/0x480
pc : [<00000000>] lr : [<c0066fc4>] psr: a0000013
sp : c02dfed0 ip : c0303b40 fp : c02eaaa0
r10: c3ccdf64 r9 : c02ea870 r8 : c02ea9d0
r7 : c3dd0f40 r6 : 00000005 r5 : 00000000 r4 : c02ea9b8
r3 : 0000000a r2 : 00000000 r1 : 00000000 r0 : c3dd0f40
Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
Control: 0005717f Table: 23db0000 DAC: 00000017
Process swapper (pid: 0, stack limit = 0xc02de270)
Stack: (0xc02dfed0 to 0xc02e0000)
fec0: c02dfed0 00000100 c02de000 00000024
fee0: 00000001 00000009 c0301188 0000000a 00000000 c0067138 00000000 c0040178
ff00: c02e6b70 00000011 00000000 00000011 00000000 00000000 00000002 c0303b40
ff20: c02eaaa4 c0303b44 c02eaaa8 c0020074 c0305860 00000011 00000014 c0068180
ff40: c02eb9c0 c02dff70 fefff000 00000011 c02f8250 2001d7e8 41069265 2001d7b4
ff60: 00000000 c0026adc ffffffff c0020b94 c0303b40 00000000 00000000 60000013
ff80: c02de000 c02eaaa0 c02e1bf8 c02f8250 2001d7e8 41069265 2001d7b4 00000000
ffa0: c0303b40 c02dffb8 c00689a8 c00689d4 60000013 ffffffff c00226a0 c0022668
ffc0: 00000000 c0316fb0 c02f7ff0 c001eb00 c02e1bec c0008988 c00084c4 00000000
ffe0: 00000000 c001eb00 00057175 c02f8278 c001ef04 20008034 00000000 00000000
[<c0066fc4>] (__rcu_process_callbacks+0x320/0x480) from [<c0067138>] (rcu_process_callbacks+0x14/0x38)
[<c0067138>] (rcu_process_callbacks+0x14/0x38) from [<c0040178>] (__do_softirq+0x84/0x130)
[<c0040178>] (__do_softirq+0x84/0x130) from [<c0020074>] (asm_do_IRQ+0x74/0x98)
[<c0020074>] (asm_do_IRQ+0x74/0x98) from [<c0068180>] (__ipipe_sync_stage+0x150/0x198)
Exception stack(0xc02dff40 to 0xc02dff88)
ff40: c02eb9c0 c02dff70 fefff000 00000011 c02f8250 2001d7e8 41069265 2001d7b4
ff60: 00000000 c0026adc ffffffff c0020b94 c0303b40 00000000 00000000 60000013
ff80: c02de000 c02eaaa0
[<c0068180>] (__ipipe_sync_stage+0x150/0x198) from [<c0026adc>] (__ipipe_grab_irq+0x58/0x74)
[<c0026adc>] (__ipipe_grab_irq+0x58/0x74) from [<c0020b94>] (__irq_svc+0x34/0x7c)
[<c0020b94>] (__irq_svc+0x34/0x7c) from [<c00689d4>] (__ipipe_unstall_root+0x48/0x58)
[<c00689d4>] (__ipipe_unstall_root+0x48/0x58) from [<c0022668>] (cpu_idle+0x50/0x9c)
[<c0022668>] (cpu_idle+0x50/0x9c) from [<c0008988>] (start_kernel+0x23c/0x294)
[<c0008988>] (start_kernel+0x23c/0x294) from [<20008034>] (0x20008034)
Code: bad PC value
---[ end trace ab8cbf29a9038c76 ]---
Kernel panic - not syncing: Fatal exception in interrupt
[<c0026694>] (unwind_backtrace+0x0/0xec) from [<c0235b04>] (panic+0x4c/0xd4)
[<c0235b04>] (panic+0x4c/0xd4) from [<c00249f4>] (die+0x18c/0x1d4)
[<c00249f4>] (die+0x18c/0x1d4) from [<c00280e8>] (__do_kernel_fault+0x64/0x84)
[<c00280e8>] (__do_kernel_fault+0x64/0x84) from [<c002834c>] (do_page_fault+0x244/0x26c)
[<c002834c>] (do_page_fault+0x244/0x26c) from [<c002023c>] (do_PrefetchAbort+0x34/0x94)
[<c002023c>] (do_PrefetchAbort+0x34/0x94) from [<c0020cd0>] (__pabt_svc+0x50/0x80)
Exception stack(0xc02dfe88 to 0xc02dfed0)
fe80: c3dd0f40 00000000 00000000 0000000a c02ea9b8 00000000
fea0: 00000005 c3dd0f40 c02ea9d0 c02ea870 c3ccdf64 c02eaaa0 c0303b40 c02dfed0
fec0: c0066fc4 00000000 a0000013 ffffffff
[<c0020cd0>] (__pabt_svc+0x50/0x80) from [<c0066fc4>] (__rcu_process_callbacks+0x320/0x480)
[<c0066fc4>] (__rcu_process_callbacks+0x320/0x480) from [<c0067138>] (rcu_process_callbacks+0x14/0x38)
[<c0067138>] (rcu_process_callbacks+0x14/0x38) from [<c0040178>] (__do_softirq+0x84/0x130)
[<c0040178>] (__do_softirq+0x84/0x130) from [<c0020074>] (asm_do_IRQ+0x74/0x98)
[<c0020074>] (asm_do_IRQ+0x74/0x98) from [<c0068180>] (__ipipe_sync_stage+0x150/0x198)
Exception stack(0xc02dff40 to 0xc02dff88)
ff40: c02eb9c0 c02dff70 fefff000 00000011 c02f8250 2001d7e8 41069265 2001d7b4
ff60: 00000000 c0026adc ffffffff c0020b94 c0303b40 00000000 00000000 60000013
ff80: c02de000 c02eaaa0
[<c0068180>] (__ipipe_sync_stage+0x150/0x198) from [<c0026adc>] (__ipipe_grab_irq+0x58/0x74)
[<c0026adc>] (__ipipe_grab_irq+0x58/0x74) from [<c0020b94>] (__irq_svc+0x34/0x7c)
[<c0020b94>] (__irq_svc+0x34/0x7c) from [<c00689d4>] (__ipipe_unstall_root+0x48/0x58)
[<c00689d4>] (__ipipe_unstall_root+0x48/0x58) from [<c0022668>] (cpu_idle+0x50/0x9c)
[<c0022668>] (cpu_idle+0x50/0x9c) from [<c0008988>] (start_kernel+0x23c/0x294)
[<c0008988>] (start_kernel+0x23c/0x294) from [<20008034>] (0x20008034)
[-- Attachment #3: config-DEBUGs-set --]
[-- Type: text/plain, Size: 35842 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.35.9
# Sun Nov 6 12:39:47 2011
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
# CONFIG_ARCH_USES_GETTIMEOFFSET is not set
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION="-xenomai"
CONFIG_LOCALVERSION_AUTO=y
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_TREE_PREEMPT_RCU is not set
# CONFIG_TINY_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=32
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_NET_NS is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
#
# Kernel Performance Events And Counters
#
# CONFIG_PERF_EVENTS is not set
# CONFIG_PERF_COUNTERS is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_COMPAT_BRK=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_CLK=y
#
# GCOV-based kernel profiling
#
# CONFIG_SLOW_WORK is not set
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_BLOCK=y
CONFIG_LBDAF=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
CONFIG_DEFAULT_NOOP=y
CONFIG_DEFAULT_IOSCHED="noop"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
# CONFIG_MUTEX_SPIN_ON_OWNER is not set
#
# Real-time sub-system
#
CONFIG_XENOMAI=y
CONFIG_XENO_GENERIC_STACKPOOL=y
CONFIG_XENO_FASTSYNCH_DEP=y
CONFIG_XENO_FASTSYNCH=y
CONFIG_XENO_OPT_NUCLEUS=y
CONFIG_XENO_OPT_PERVASIVE=y
CONFIG_XENO_OPT_PRIOCPL=y
CONFIG_XENO_OPT_PIPELINE_HEAD=y
# CONFIG_XENO_OPT_SCHED_CLASSES is not set
CONFIG_XENO_OPT_PIPE=y
CONFIG_XENO_OPT_VFILE=y
CONFIG_XENO_OPT_PIPE_NRDEV=32
CONFIG_XENO_OPT_REGISTRY_NRSLOTS=512
CONFIG_XENO_OPT_SYS_HEAPSZ=256
CONFIG_XENO_OPT_SYS_STACKPOOLSZ=128
CONFIG_XENO_OPT_SEM_HEAPSZ=12
CONFIG_XENO_OPT_GLOBAL_SEM_HEAPSZ=12
CONFIG_XENO_OPT_STATS=y
CONFIG_XENO_OPT_DEBUG=y
# CONFIG_XENO_OPT_DEBUG_NUCLEUS is not set
# CONFIG_XENO_OPT_DEBUG_XNLOCK is not set
# CONFIG_XENO_OPT_DEBUG_QUEUES is not set
# CONFIG_XENO_OPT_DEBUG_REGISTRY is not set
# CONFIG_XENO_OPT_DEBUG_TIMERS is not set
# CONFIG_XENO_OPT_DEBUG_SYNCH_RELAX is not set
CONFIG_XENO_OPT_WATCHDOG=y
CONFIG_XENO_OPT_WATCHDOG_TIMEOUT=4
CONFIG_XENO_OPT_SHIRQ=y
CONFIG_XENO_OPT_SELECT=y
CONFIG_XENO_OPT_HOSTRT=y
#
# Timing
#
# CONFIG_XENO_OPT_TIMING_PERIODIC is not set
CONFIG_XENO_OPT_TIMING_VIRTICK=1000
CONFIG_XENO_OPT_TIMING_SCHEDLAT=0
#
# Scalability
#
# CONFIG_XENO_OPT_SCALABLE_SCHED is not set
CONFIG_XENO_OPT_TIMER_LIST=y
# CONFIG_XENO_OPT_TIMER_HEAP is not set
# CONFIG_XENO_OPT_TIMER_WHEEL is not set
#
# Machine
#
CONFIG_IPIPE_WANT_PREEMPTIBLE_SWITCH=y
CONFIG_XENO_HW_FPU=y
CONFIG_XENO_HW_UNLOCKED_SWITCH=y
#
# Interfaces
#
CONFIG_XENO_SKIN_NATIVE=y
CONFIG_XENO_OPT_NATIVE_PERIOD=0
CONFIG_XENO_OPT_NATIVE_PIPE=y
CONFIG_XENO_OPT_NATIVE_PIPE_BUFSZ=1024
CONFIG_XENO_OPT_NATIVE_SEM=y
CONFIG_XENO_OPT_NATIVE_EVENT=y
CONFIG_XENO_OPT_NATIVE_MUTEX=y
CONFIG_XENO_OPT_NATIVE_COND=y
CONFIG_XENO_OPT_NATIVE_QUEUE=y
CONFIG_XENO_OPT_NATIVE_BUFFER=y
CONFIG_XENO_OPT_NATIVE_HEAP=y
CONFIG_XENO_OPT_NATIVE_ALARM=y
CONFIG_XENO_OPT_NATIVE_MPS=y
# CONFIG_XENO_OPT_NATIVE_INTR is not set
CONFIG_XENO_OPT_DEBUG_NATIVE=y
CONFIG_XENO_SKIN_POSIX=y
CONFIG_XENO_OPT_POSIX_PERIOD=0
# CONFIG_XENO_OPT_POSIX_SHM is not set
# CONFIG_XENO_OPT_POSIX_INTR is not set
CONFIG_XENO_OPT_POSIX_SELECT=y
CONFIG_XENO_OPT_DEBUG_POSIX=y
# CONFIG_XENO_SKIN_PSOS is not set
# CONFIG_XENO_SKIN_UITRON is not set
# CONFIG_XENO_SKIN_VRTX is not set
# CONFIG_XENO_SKIN_VXWORKS is not set
# CONFIG_XENO_OPT_NOWARN_DEPRECATED is not set
CONFIG_XENO_SKIN_RTDM=y
CONFIG_XENO_OPT_RTDM_PERIOD=0
CONFIG_XENO_OPT_RTDM_FILDES=128
CONFIG_XENO_OPT_RTDM_SELECT=y
# CONFIG_XENO_OPT_DEBUG_RTDM is not set
CONFIG_XENO_OPT_DEBUG_RTDM_APPL=y
#
# Drivers
#
#
# Serial drivers
#
# CONFIG_XENO_DRIVERS_16550A is not set
#
# Testing drivers
#
CONFIG_XENO_DRIVERS_TIMERBENCH=y
# CONFIG_XENO_DRIVERS_KLATENCY is not set
# CONFIG_XENO_DRIVERS_IRQBENCH is not set
CONFIG_XENO_DRIVERS_SWITCHTEST=y
# CONFIG_XENO_DRIVERS_RTDMTEST is not set
#
# CAN drivers
#
# CONFIG_XENO_DRIVERS_CAN is not set
#
# ANALOGY drivers
#
# CONFIG_XENO_DRIVERS_ANALOGY is not set
#
# Real-time IPC drivers
#
# CONFIG_XENO_DRIVERS_RTIPC is not set
CONFIG_FREEZER=y
#
# System Type
#
CONFIG_MMU=y
# CONFIG_ARCH_AAEC2000 is not set
# CONFIG_ARCH_INTEGRATOR is not set
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_VEXPRESS is not set
CONFIG_ARCH_AT91=y
# CONFIG_ARCH_BCMRING is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_CNS3XXX is not set
# CONFIG_ARCH_GEMINI is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_MXC is not set
# CONFIG_ARCH_STMP3XXX is not set
# CONFIG_ARCH_NETX is not set
# CONFIG_ARCH_H720X is not set
# CONFIG_ARCH_IOP13XX is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IOP33X is not set
# CONFIG_ARCH_IXP23XX is not set
# CONFIG_ARCH_IXP2000 is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_L7200 is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_KIRKWOOD is not set
# CONFIG_ARCH_LOKI is not set
# CONFIG_ARCH_MV78XX0 is not set
# CONFIG_ARCH_ORION5X is not set
# CONFIG_ARCH_MMP is not set
# CONFIG_ARCH_KS8695 is not set
# CONFIG_ARCH_NS9XXX is not set
# CONFIG_ARCH_W90X900 is not set
# CONFIG_ARCH_NUC93X is not set
# CONFIG_ARCH_PNX4008 is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_MSM is not set
# CONFIG_ARCH_SHMOBILE is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C2410 is not set
# CONFIG_ARCH_S3C64XX is not set
# CONFIG_ARCH_S5P6440 is not set
# CONFIG_ARCH_S5P6442 is not set
# CONFIG_ARCH_S5PC100 is not set
# CONFIG_ARCH_S5PV210 is not set
# CONFIG_ARCH_SHARK is not set
# CONFIG_ARCH_LH7A40X is not set
# CONFIG_ARCH_U300 is not set
# CONFIG_ARCH_U8500 is not set
# CONFIG_ARCH_NOMADIK is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_ARCH_OMAP is not set
# CONFIG_PLAT_SPEAR is not set
CONFIG_HAVE_AT91_USART3=y
CONFIG_HAVE_AT91_USART4=y
CONFIG_HAVE_AT91_USART5=y
#
# Atmel AT91 System-on-Chip
#
# CONFIG_ARCH_AT91RM9200 is not set
# CONFIG_ARCH_AT91SAM9260 is not set
# CONFIG_ARCH_AT91SAM9261 is not set
# CONFIG_ARCH_AT91SAM9G10 is not set
# CONFIG_ARCH_AT91SAM9263 is not set
# CONFIG_ARCH_AT91SAM9RL is not set
CONFIG_ARCH_AT91SAM9G20=y
# CONFIG_ARCH_AT91SAM9G45 is not set
# CONFIG_ARCH_AT91CAP9 is not set
# CONFIG_ARCH_AT572D940HF is not set
# CONFIG_ARCH_AT91X40 is not set
CONFIG_AT91_PMC_UNIT=y
#
# AT91SAM9G20 Board Type
#
# CONFIG_MACH_AT91SAM9G20EK is not set
# CONFIG_MACH_AT91SAM9G20EK_2MMC is not set
# CONFIG_MACH_CPU9G20 is not set
# CONFIG_MACH_PORTUXG20 is not set
# CONFIG_MACH_STAMP9G20 is not set
CONFIG_MACH_ELECTRUM_100=y
#
# Adeos I-pipe Options
#
CONFIG_IPIPE_AT91_TC=0
#
# AT91 Board Options
#
#
# AT91 Feature Selections
#
CONFIG_AT91_PROGRAMMABLE_CLOCKS=y
# CONFIG_AT91_SLOW_CLOCK is not set
CONFIG_AT91_TIMER_HZ=1000
# CONFIG_AT91_EARLY_DBGU is not set
CONFIG_AT91_EARLY_USART0=y
# CONFIG_AT91_EARLY_USART1 is not set
# CONFIG_AT91_EARLY_USART2 is not set
# CONFIG_AT91_EARLY_USART3 is not set
# CONFIG_AT91_EARLY_USART4 is not set
# CONFIG_AT91_EARLY_USART5 is not set
CONFIG_IPIPE_ARM_KUSER_TSC=y
#
# Processor Type
#
CONFIG_CPU_ARM926T=y
CONFIG_CPU_32v5=y
CONFIG_CPU_ABRT_EV5TJ=y
CONFIG_CPU_PABRT_LEGACY=y
CONFIG_CPU_CACHE_VIVT=y
CONFIG_CPU_COPY_V4WB=y
CONFIG_CPU_TLB_V4WBI=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
# CONFIG_ARM_THUMB is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_DISABLE is not set
# CONFIG_CPU_DCACHE_WRITETHROUGH is not set
CONFIG_CPU_CACHE_ROUND_ROBIN=y
CONFIG_ARM_L1_CACHE_SHIFT=5
CONFIG_ARM_FCSE=y
# CONFIG_ARM_FCSE_GUARANTEED is not set
CONFIG_ARM_FCSE_BEST_EFFORT=y
CONFIG_ARM_FCSE_PREEMPT_FLUSH=y
CONFIG_ARM_FCSE_MESSAGES=y
CONFIG_ARM_FCSE_DEBUG=y
#
# Bus support
#
# CONFIG_PCI_SYSCALL is not set
# CONFIG_ARCH_SUPPORTS_MSI is not set
# CONFIG_PCCARD is not set
#
# Kernel Features
#
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
CONFIG_IPIPE=y
CONFIG_IPIPE_DOMAINS=4
CONFIG_IPIPE_DELAYED_ATOMICSW=y
# CONFIG_IPIPE_UNMASKED_CONTEXT_SWITCH is not set
CONFIG_HAVE_IPIPE_HOSTRT=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_HZ=1000
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
# CONFIG_HIGHMEM is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=999999
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=0
CONFIG_VIRT_TO_BUS=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
# CONFIG_LEDS is not set
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
#
# Boot options
#
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_CMDLINE="mem=64M console=ttyS0,115200"
# CONFIG_CMDLINE_FORCE is not set
# CONFIG_XIP_KERNEL is not set
# CONFIG_KEXEC is not set
#
# CPU Power Management
#
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
#
# Floating point emulation
#
#
# At least one emulation must be selected
#
CONFIG_FPE_NWFPE=y
# CONFIG_FPE_NWFPE_XP is not set
# CONFIG_FPE_FASTFPE is not set
# CONFIG_VFP is not set
#
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set
#
# Power management options
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
CONFIG_PM_SLEEP=y
CONFIG_SUSPEND_NVS=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_APM_EMULATION=y
# CONFIG_PM_RUNTIME is not set
CONFIG_PM_OPS=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
# CONFIG_IP_PNP_DHCP is not set
CONFIG_IP_PNP_BOOTP=y
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_WIRELESS is not set
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_DEVTMPFS is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
#
# DRBD disabled because PROC_FS, INET or CONNECTOR not selected
#
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MG_DISK is not set
CONFIG_MISC_DEVICES=y
# CONFIG_AD525X_DPOT is not set
CONFIG_ATMEL_TCLIB=y
# CONFIG_ICS932S401 is not set
# CONFIG_ATMEL_SSC is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_ISL29003 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_DS1682 is not set
# CONFIG_TI_DAC7512 is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_IWMC3200TOP is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# CONFIG_SCSI_DMA is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
# CONFIG_MARVELL_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_QSEMI_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_SMSC_PHY is not set
# CONFIG_BROADCOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_REALTEK_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_STE10XP is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_FIXED_PHY is not set
# CONFIG_MDIO_BITBANG is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_MACB=y
# CONFIG_AX88796 is not set
# CONFIG_SMC91X is not set
# CONFIG_DM9000 is not set
# CONFIG_ENC28J60 is not set
# CONFIG_ETHOC is not set
# CONFIG_SMC911X is not set
# CONFIG_SMSC911X is not set
# CONFIG_DNET is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
# CONFIG_B44 is not set
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_WLAN is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_WAN is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=320
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=240
# CONFIG_INPUT_JOYDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ATKBD is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_GPIO=y
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_N_GSM is not set
#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_ATMEL=y
CONFIG_SERIAL_ATMEL_CONSOLE=y
CONFIG_SERIAL_ATMEL_PDC=y
# CONFIG_SERIAL_ATMEL_TTYAT is not set
# CONFIG_SERIAL_MAX3100 is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=16
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_R3964 is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_RAMOOPS is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_HELPER_AUTO=y
#
# I2C Hardware Bus support
#
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_DESIGNWARE is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
CONFIG_SPI_ATMEL=y
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_DESIGNWARE is not set
#
# SPI Protocol Masters
#
CONFIG_SPI_SPIDEV=y
# CONFIG_SPI_TLE62X0 is not set
#
# PPS support
#
# CONFIG_PPS is not set
CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
#
# Memory mapped GPIO expanders:
#
# CONFIG_GPIO_IT8761E is not set
#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_ADP5588 is not set
#
# PCI GPIO expanders:
#
#
# SPI GPIO expanders:
#
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MCP23S08 is not set
# CONFIG_GPIO_MC33880 is not set
#
# AC97 GPIO expanders:
#
#
# MODULbus GPIO expanders:
#
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB=y
CONFIG_SSB_SDIOHOST_POSSIBLE=y
# CONFIG_SSB_SDIOHOST is not set
# CONFIG_SSB_DEBUG is not set
CONFIG_MFD_SUPPORT=y
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_TC35892 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_MC13783 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_EZX_PCAP is not set
# CONFIG_AB8500_CORE is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_SUPPORT is not set
#
# Graphics support
#
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
# CONFIG_USB_ARCH_HAS_EHCI is not set
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_HCD_SSB is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HWA_HCD is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_GADGET_MUSB_HDRC is not set
#
# USB Device Class drivers
#
CONFIG_USB_ACM=m
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
# CONFIG_USB_GADGET_DEBUG_FILES is not set
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_SELECTED=y
CONFIG_USB_GADGET_AT91=y
CONFIG_USB_AT91=y
# CONFIG_USB_GADGET_ATMEL_USBA is not set
# CONFIG_USB_GADGET_FSL_USB2 is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_PXA25X is not set
# CONFIG_USB_GADGET_R8A66597 is not set
# CONFIG_USB_GADGET_PXA27X is not set
# CONFIG_USB_GADGET_S3C_HSOTG is not set
# CONFIG_USB_GADGET_IMX is not set
# CONFIG_USB_GADGET_S3C2410 is not set
# CONFIG_USB_GADGET_M66592 is not set
# CONFIG_USB_GADGET_AMD5536UDC is not set
# CONFIG_USB_GADGET_FSL_QE is not set
# CONFIG_USB_GADGET_CI13XXX is not set
# CONFIG_USB_GADGET_NET2280 is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LANGWELL is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
# CONFIG_USB_GADGET_DUALSPEED is not set
CONFIG_USB_ZERO=m
# CONFIG_USB_AUDIO is not set
CONFIG_USB_ETH=m
CONFIG_USB_ETH_RNDIS=y
# CONFIG_USB_ETH_EEM is not set
CONFIG_USB_GADGETFS=m
# CONFIG_USB_FUNCTIONFS is not set
CONFIG_USB_FILE_STORAGE=m
# CONFIG_USB_FILE_STORAGE_TEST is not set
# CONFIG_USB_MASS_STORAGE is not set
CONFIG_USB_G_SERIAL=m
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_NOKIA is not set
# CONFIG_USB_G_MULTI is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_WEBCAM is not set
#
# OTG and related infrastructure
#
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ULPI is not set
# CONFIG_NOP_USB_XCEIV is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
CONFIG_MMC_TEST=y
#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_SDHCI is not set
CONFIG_MMC_AT91=y
# CONFIG_MMC_ATMELMCI is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_DS3234 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_AT91SAM9=y
CONFIG_RTC_DRV_AT91SAM9_RTT=0
CONFIG_RTC_DRV_AT91SAM9_GPBR=0
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_STAGING is not set
#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT23=y
# CONFIG_EXT4_FS_XATTR is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set
# CONFIG_MISC_FILESYSTEMS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set
#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_IPIPE_DEBUG=y
CONFIG_IPIPE_DEBUG_CONTEXT=y
CONFIG_IPIPE_DEBUG_INTERNAL=y
# CONFIG_IPIPE_TRACE is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
# CONFIG_PAGE_POISONING is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_ARM_UNWIND=y
CONFIG_DEBUG_USER=y
CONFIG_DEBUG_ERRORS=y
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_LL is not set
# CONFIG_OC_ETM is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
# CONFIG_DEFAULT_SECURITY_SMACK is not set
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
# CONFIG_CRYPTO is not set
# CONFIG_BINARY_PRINTF is not set
#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_LAST_BIT=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_NLATTR=y
CONFIG_GENERIC_ATOMIC64=y
^ permalink raw reply
* Re: [Qemu-devel] [PATCH] KVM: Add wrapper script around QEMU to test kernels
From: Pekka Enberg @ 2011-11-06 18:58 UTC (permalink / raw)
To: Ted Ts'o, Anthony Liguori, Avi Kivity, Pekka Enberg,
kvm@vger.kernel.org list, linux-kernel@vger.kernel.org List,
qemu-devel Developers, Alexander Graf, Blue Swirl,
Américo Wang, Ingo Molnar, Linus Torvalds
In-Reply-To: <CAOJsxLHvYo5zA+_m-AXuZHjAcGKE5q0ytmPCZ0Gye52LWq1p9Q@mail.gmail.com>
On Sun, Nov 6, 2011 at 8:54 PM, Pekka Enberg <penberg@kernel.org> wrote:
>> So integrating kvm-tool into the kernel isn't going to work as a free
>> pass to make non-backwards compatible changes to the KVM user/kernel
>> interface. Given that, why bloat the kernel source tree size?
>
> Ted, I'm confused. Making backwards incompatible ABI changes has never
> been on the table. Why are you bringing it up?
And btw, KVM tool is not a random userspace project - it was designed
to live in tools/kvm from the beginning. I've explained the technical
rationale for sharing kernel code here:
https://lkml.org/lkml/2011/11/4/150
Please also see Ingo's original rant that started the project:
http://thread.gmane.org/gmane.linux.kernel/962051/focus=962620
Pekka
^ permalink raw reply
* Re: [PATCH] agp: Enable all supported rates for graphic cards
From: Corbin Simpson @ 2011-11-06 18:55 UTC (permalink / raw)
To: Tormod Volden; +Cc: dri-devel
In-Reply-To: <CAArsGaaojCwA1NK5Tg2j2EVwqKjoLu31vbPF0_npt30x9e8QnQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4121 bytes --]
Thanks for writing it!
Reviewed-by: Corbin Simpson <MostAwesomeDude@gmail.com>
Sending from a mobile, pardon my terseness. ~ C.
On Nov 6, 2011 10:39 AM, "Tormod Volden" <lists.tormod@gmail.com> wrote:
> On Sun, Nov 6, 2011 at 4:37 PM, Corbin Simpson
> <mostawesomedude@gmail.com> wrote:
> > Trusting the spec worries me; could this break anybody?
>
> It will allow the user to override possibly safer default settings. If
> a user has specified, say, 2x in his xorg.conf and this was not
> honored because the card only reported 4x, this patch would finally
> give him the 2x he is asking for. If 2x turns out to not work, he will
> suddenly have problems. But the solution would be to fix his
> xorg.conf. Up till now he might be thinking 2x works fine, while he
> was actually getting another rate.
>
> Generally, the default rate is defined by the DDX and the patch does
> not change these policies. However, with the patch we may actually
> apply the default value, instead of an undefined "0x" (i.e. the case
> when the DDX sets 1x or 2x by default, but the card says only 4x). The
> spec (I have checked section 6.1.10) does not say anything about
> writing a zero rate, and I don't know what the silicon does. I don't
> know of any way to read out the resulting speed. Is there any simple
> agp benchmarking tools?
>
> Of course, it would be good if more people who currently see "0x" in
> dmesg would try this patch.
>
> Note that Dave Jones did the same for bridges in
> 28af24bb8470c7d0573b703a2955548b73a6c066 to get rid of "0x" cases.
>
> >
> > Is there any reason to use the not-so-magic numbers instead of the named
> > constants?
>
> I followed the style of the surrounding code. I can follow up with a
> patch using named constants everywhere if that would be desired.
>
> Thanks for looking at it!
> Tormod
>
>
> >
> > Sending from a mobile, pardon my terseness. ~ C.
> >
> > On Nov 6, 2011 7:03 AM, "Tormod Volden" <lists.tormod@gmail.com> wrote:
> >>
> >> From: Tormod Volden <debian.tormod@gmail.com>
> >>
> >> Some cards report that they support only 4x, in which case they
> >> should support 2x and 1x as well, according to the AGP spec.
> >>
> >> Otherwise a requested 1x or 2x rate will result in 0 being set:
> >>
> >> agpgart-via 0000:00:00.0: putting AGP V2 device into 0x mode
> >>
> >> For instance ProSavage KN133 [5333:8d02] only reports 4x.
> >>
> >> Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
> >> ---
> >> drivers/char/agp/generic.c | 18 ++++++++++++++++++
> >> 1 files changed, 18 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/drivers/char/agp/generic.c b/drivers/char/agp/generic.c
> >> index b072648..c5d04e5 100644
> >> --- a/drivers/char/agp/generic.c
> >> +++ b/drivers/char/agp/generic.c
> >> @@ -526,6 +526,24 @@ static void agp_v2_parse_one(u32 *requested_mode,
> u32
> >> *bridge_agpstat, u32 *vga_
> >> break;
> >> }
> >>
> >> + /* Some graphic cards report they only support 4x, however the
> AGP
> >> 2.0 spec
> >> + * (section 4.1.1) says components must support the lower speeds
> >> as well.
> >> + */
> >> + switch (*vga_agpstat & 7) {
> >> + case 4:
> >> + *vga_agpstat |= (AGPSTAT2_2X | AGPSTAT2_1X);
> >> + printk(KERN_INFO PFX "Graphics card claims to only
> support
> >> x4 rate. "
> >> + "Fixing up support for x2 & x1\n");
> >> + break;
> >> + case 2:
> >> + *vga_agpstat |= AGPSTAT2_1X;
> >> + printk(KERN_INFO PFX "Graphics card claims to only
> support
> >> x2 rate. "
> >> + "Fixing up support for x1\n");
> >> + break;
> >> + default:
> >> + break;
> >> + }
> >> +
> >> /* Check the speed bits make sense. Only one should be set. */
> >> tmp = *requested_mode & 7;
> >> switch (tmp) {
> >> --
> >> 1.7.5.4
> >>
> >> _______________________________________________
> >> dri-devel mailing list
> >> dri-devel@lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
>
[-- Attachment #1.2: Type: text/html, Size: 5548 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply
* Re: [Qemu-devel] [PATCH v2 4/7] block: take lock around bdrv_read implementations
From: Avi Kivity @ 2011-11-06 17:29 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: qemu-devel
In-Reply-To: <4EB6C312.2020402@redhat.com>
On 11/06/2011 07:25 PM, Paolo Bonzini wrote:
> On 11/06/2011 03:27 PM, Avi Kivity wrote:
>> On 10/20/2011 01:16 PM, Paolo Bonzini wrote:
>>> This does the first part of the conversion to coroutines, by
>>> wrapping bdrv_read implementations to take the read side of the
>>> rwlock.
>>>
>>> Drivers that implement bdrv_read rather than bdrv_co_readv can
>>> then benefit from asynchronous operation (at least if the underlying
>>> protocol supports it, which is not the case for raw-win32), even
>>> though they still operate with a bounce buffer.
>>>
>>> raw-win32 does not need the lock, because it cannot yield.
>>> nbd also doesn't probably, but better be safe.
>>
>> This patch (2914caa088e3fbbd) breaks autotest when a guest reboots after
>> install; instead of rebooting, the guest is stuck in the bootloader or
>> kernel.
>
> Are any of these formats used by autotest?
>
It's configurable; in my case, qcow2.
> block/bochs.c | 13 ++++++++++++-
> block/cloop.c | 13 ++++++++++++-
> block/cow.c | 13 ++++++++++++-
> block/dmg.c | 13 ++++++++++++-
> block/nbd.c | 13 ++++++++++++-
> block/parallels.c | 13 ++++++++++++-
> block/vmdk.c | 13 ++++++++++++-
> block/vpc.c | 13 ++++++++++++-
> block/vvfat.c | 13 ++++++++++++-
> 9 files changed, 108 insertions(+), 9 deletions(-)
>
So no.
> Perhaps the failure is only reproduced 80-90% of the time and this
> screws up the bisection.
I thought I checked the before/after commit, but looking at the
diffstat, that's doesn't make sense.
On a related note, booting with -cdrom http://blah seems broken.
--
error compiling committee.c: too many arguments to function
^ permalink raw reply
* Re: [Qemu-devel] [PATCH] KVM: Add wrapper script around QEMU to test kernels
From: Pekka Enberg @ 2011-11-06 18:54 UTC (permalink / raw)
To: Ted Ts'o, Anthony Liguori, Avi Kivity, Pekka Enberg,
kvm@vger.kernel.org list, linux-kernel@vger.kernel.org List,
qemu-devel Developers, Alexander Graf, Blue Swirl,
Américo Wang, Ingo Molnar, Linus Torvalds
In-Reply-To: <20111106183132.GA4500@thunk.org>
On Sun, Nov 06, 2011 at 11:08:10AM -0600, Anthony Liguori wrote:
>> I'm quite happy with KVM tool and hope they continue working on it.
>> My only real wish is that they wouldn't copy QEMU so much and would
>> try bolder things that are fundamentally different from QEMU.
On Sun, Nov 6, 2011 at 8:31 PM, Ted Ts'o <tytso@mit.edu> wrote:
> My big wish is that they don't try to merge the KVM tool into the
> kernel code. It's a separate userspace project, and there's no reason
> for it to be bundled with kernel code. It just makes the kernel
> sources larger. The mere fact that qemu-kvm exists means that the KVM
> interface has to remain backward compatible; it *is* an ABI.
>
> So integrating kvm-tool into the kernel isn't going to work as a free
> pass to make non-backwards compatible changes to the KVM user/kernel
> interface. Given that, why bloat the kernel source tree size?
Ted, I'm confused. Making backwards incompatible ABI changes has never
been on the table. Why are you bringing it up?
Pekka
^ permalink raw reply
* [U-Boot] From Mr.Younes Amadou .
From: amadou @ 2011-11-06 18:54 UTC (permalink / raw)
To: u-boot
^ permalink raw reply
* [PATCH] drm/i915/ringbuffer: kill snb blt workaround
From: Kenneth Graunke @ 2011-11-06 18:50 UTC (permalink / raw)
To: intel-gfx; +Cc: Daniel Vetter
In-Reply-To: <20111106180318.GB3126@phenom.ffwll.local>
From: Daniel Vetter <daniel.vetter@ffwll.ch>
This was just to facilitate product enablement with pre-production hw.
Allows us to kill quite a bit of cruft.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Eric Anholt <eric@anholt.net>
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 81 +------------------------------
1 files changed, 2 insertions(+), 79 deletions(-)
Thanks Daniel, I missed that! This is much nicer.
Here's your original patch rebased against drm-intel-next. I dropped the
first hunk because the render ring now uses the cleanup hook for PIPE_CONTROL.
Otherwise, it's the same.
diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
index ca70e2f..0602bb6 100644
--- a/drivers/gpu/drm/i915/intel_ringbuffer.c
+++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
@@ -1345,79 +1345,13 @@ blt_ring_put_irq(struct intel_ring_buffer *ring)
GEN6_BLITTER_USER_INTERRUPT);
}
-
-/* Workaround for some stepping of SNB,
- * each time when BLT engine ring tail moved,
- * the first command in the ring to be parsed
- * should be MI_BATCH_BUFFER_START
- */
-#define NEED_BLT_WORKAROUND(dev) \
- (IS_GEN6(dev) && (dev->pdev->revision < 8))
-
-static inline struct drm_i915_gem_object *
-to_blt_workaround(struct intel_ring_buffer *ring)
-{
- return ring->private;
-}
-
-static int blt_ring_init(struct intel_ring_buffer *ring)
-{
- if (NEED_BLT_WORKAROUND(ring->dev)) {
- struct drm_i915_gem_object *obj;
- u32 *ptr;
- int ret;
-
- obj = i915_gem_alloc_object(ring->dev, 4096);
- if (obj == NULL)
- return -ENOMEM;
-
- ret = i915_gem_object_pin(obj, 4096, true);
- if (ret) {
- drm_gem_object_unreference(&obj->base);
- return ret;
- }
-
- ptr = kmap(obj->pages[0]);
- *ptr++ = MI_BATCH_BUFFER_END;
- *ptr++ = MI_NOOP;
- kunmap(obj->pages[0]);
-
- ret = i915_gem_object_set_to_gtt_domain(obj, false);
- if (ret) {
- i915_gem_object_unpin(obj);
- drm_gem_object_unreference(&obj->base);
- return ret;
- }
-
- ring->private = obj;
- }
-
- return init_ring_common(ring);
-}
-
-static int blt_ring_begin(struct intel_ring_buffer *ring,
- int num_dwords)
-{
- if (ring->private) {
- int ret = intel_ring_begin(ring, num_dwords+2);
- if (ret)
- return ret;
-
- intel_ring_emit(ring, MI_BATCH_BUFFER_START);
- intel_ring_emit(ring, to_blt_workaround(ring)->gtt_offset);
-
- return 0;
- } else
- return intel_ring_begin(ring, 4);
-}
-
static int blt_ring_flush(struct intel_ring_buffer *ring,
u32 invalidate, u32 flush)
{
uint32_t cmd;
int ret;
- ret = blt_ring_begin(ring, 4);
+ ret = intel_ring_begin(ring, 4);
if (ret)
return ret;
@@ -1432,22 +1366,12 @@ static int blt_ring_flush(struct intel_ring_buffer *ring,
return 0;
}
-static void blt_ring_cleanup(struct intel_ring_buffer *ring)
-{
- if (!ring->private)
- return;
-
- i915_gem_object_unpin(ring->private);
- drm_gem_object_unreference(ring->private);
- ring->private = NULL;
-}
-
static const struct intel_ring_buffer gen6_blt_ring = {
.name = "blt ring",
.id = RING_BLT,
.mmio_base = BLT_RING_BASE,
.size = 32 * PAGE_SIZE,
- .init = blt_ring_init,
+ .init = init_ring_common,
.write_tail = ring_write_tail,
.flush = blt_ring_flush,
.add_request = gen6_add_request,
@@ -1455,7 +1379,6 @@ static const struct intel_ring_buffer gen6_blt_ring = {
.irq_get = blt_ring_get_irq,
.irq_put = blt_ring_put_irq,
.dispatch_execbuffer = gen6_ring_dispatch_execbuffer,
- .cleanup = blt_ring_cleanup,
.sync_to = gen6_blt_ring_sync_to,
.semaphore_register = {MI_SEMAPHORE_SYNC_BR,
MI_SEMAPHORE_SYNC_BV,
--
1.7.7.1
^ permalink raw reply related
* Re: Linux Route Cache performance tests
From: Eric Dumazet @ 2011-11-06 18:48 UTC (permalink / raw)
To: Paweł Staszewski; +Cc: Linux Network Development list
In-Reply-To: <4EB6D1D8.8040604@itcare.pl>
Le dimanche 06 novembre 2011 à 19:28 +0100, Paweł Staszewski a écrit :
> W dniu 2011-11-06 18:29, Eric Dumazet pisze:
> > Le dimanche 06 novembre 2011 à 16:57 +0100, Paweł Staszewski a écrit :
> >> Hello
> >>
> >>
> >>
> >> I make some networking performance tests for Linux 3.1
> >>
> >> Configuration:
> >>
> >> Linux (pktget) ----> Linux (router) ----> Linux (Sink)
> >>
> >> pktgen config:
> >> clone_skb 32
> >> pkt_size 64
> >> delay 0
> >>
> >> pgset "flag IPDST_RND"
> >> pgset "dst_min 10.0.0.0"
> >> pgset "dst_max 10.18.255.255"
> >> pgset "config 1"
> >> pgset "flows 256"
> >> pgset "flowlen 8"
> >>
> >> TX performance for this host:
> >> eth0: RX: 0.00 P/s TX: 12346107.73 P/s TOTAL:
> >> 12346107.73 P/s
> >>
> >> On Linux (router):
> >> grep . /proc/sys/net/ipv4/route/*
> >> /proc/sys/net/ipv4/route/error_burst:500
> >> /proc/sys/net/ipv4/route/error_cost:100
> >> grep: /proc/sys/net/ipv4/route/flush: Permission denied
> >> /proc/sys/net/ipv4/route/gc_elasticity:4
> >> /proc/sys/net/ipv4/route/gc_interval:60
> >> /proc/sys/net/ipv4/route/gc_min_interval:0
> >> /proc/sys/net/ipv4/route/gc_min_interval_ms:500
> >> /proc/sys/net/ipv4/route/gc_thresh:2000000
> >> /proc/sys/net/ipv4/route/gc_timeout:60
> >> /proc/sys/net/ipv4/route/max_size:8388608
> >> /proc/sys/net/ipv4/route/min_adv_mss:256
> >> /proc/sys/net/ipv4/route/min_pmtu:552
> >> /proc/sys/net/ipv4/route/mtu_expires:600
> >> /proc/sys/net/ipv4/route/redirect_load:2
> >> /proc/sys/net/ipv4/route/redirect_number:9
> >> /proc/sys/net/ipv4/route/redirect_silence:2048
> >>
> >> For the first 30secs maybee more router is forwarding ~5Mpps to the
> >> Linux (Sink)
> >> and some stats for this forst 30secs in attached image:
> >>
> >> http://imageshack.us/photo/my-images/684/test1ih.png/
> >>
> >> Left up - pktgen linux
> >> left down - Linux router (htop)
> >> Right up - Linux router (bwm-ng - showing pps)
> >> Right down - Linux router (lnstat)
> >>
> >>
> >> And all is good - performance 5Mpps until Linux router will reach ~1kk
> >> entries
> >> What You can see on next attached image:
> >>
> >> http://imageshack.us/photo/my-images/24/test2id.png/
> >>
> >> Forwarding performance drops from 5Mpps to 1,8Mpps
> >> And after 3 - 4 minutes it will stop on 0,7Mpps
> >>
> >>
> >> After flushing the route cache performance increase from 0.7Mpps to 6Mpps
> >> What You can see on next attached image:
> >>
> >> http://imageshack.us/photo/my-images/197/test3r.png/
> >>
> >> Is it possible to turn off route cache ? and see what performance will
> >> be without caching
> >>
> > Route cache cannot handle DDOS situation, since it will be filled,
> > unless you have a lot of memory.
> hmm
> but what is DDOS situation for route cache ? new entries per sec ? total
> amount of entries 1,2kk in my tests ?
> Look sometimes in normal scenario You can hit
> 1245072 route cache entries
> This is normal for BGP configurations.
>
Then figure out the right tunables for your machine ?
Its not a laptop or average server setup, so you need to allow your
kernel to consume a fair amount of memory for the route cache.
Or accept low performance :(
> The performance of route cache is ok to the point where we reach more
> than 1245072 entries.
> Router is starting forwarding packets with 5Mpps and ends at about
> 0.7Mpps when more than 1245072 entries is reached.
> For my scenario
> Random ip generation start at: 10.0.0.0 ends on 10.18.255.255
> this is 1170450 random ip's
>
I have no problem with 4 millions entries in route cache, with full
performance, not 80%.
You currently have one hash table with 524288 entries
(before you changed /proc/sys/net/ipv4/route/gc_thresh)
Its not optimal for your workload, because you have many slots with 4
chained items, performance sucks.
You have to boot your machine with "rhash_entries=2097152", so that
average chain length is less than 1
Your problem is then solved :
# grep . /proc/sys/net/ipv4/route/*
/proc/sys/net/ipv4/route/error_burst:5000
/proc/sys/net/ipv4/route/error_cost:1000
/proc/sys/net/ipv4/route/gc_elasticity:8
/proc/sys/net/ipv4/route/gc_min_interval:0
/proc/sys/net/ipv4/route/gc_min_interval_ms:500
/proc/sys/net/ipv4/route/gc_thresh:2097152
/proc/sys/net/ipv4/route/gc_timeout:300
/proc/sys/net/ipv4/route/max_size:33554432
/proc/sys/net/ipv4/route/min_adv_mss:256
/proc/sys/net/ipv4/route/min_pmtu:552
/proc/sys/net/ipv4/route/mtu_expires:600
/proc/sys/net/ipv4/route/redirect_load:20
/proc/sys/net/ipv4/route/redirect_number:9
/proc/sys/net/ipv4/route/redirect_silence:20480
^ permalink raw reply
* Re: [lm-sensors] Intel 2500K stock fan control
From: Jean Delvare @ 2011-11-06 18:45 UTC (permalink / raw)
To: lm-sensors
In-Reply-To: <4EB6CC0B.8050909@gmx.de>
On Sun, 06 Nov 2011 19:03:55 +0100, Soeren D. Schulze wrote:
> It's me with my NCT6776 again.
>
> It doesn't seem to be the driver that is causing problems.
>
> When I force the PWM to full duty cycle at low CPU temperature, I get
> about 2200 RPM. I get the same thing when I disconnect the PWM pin
> completely (so apparently the driver sets the PWM duty cycle correctly).
> Voltage on the supply pin of the fan is 12 V.
>
> When put load on the system and CPU temperature rises, though, the fan
> RPM rise up to 2800. The question is: What is the reason for this RPM
> rise? It can't be the PWM signal, as the PWM pin is disconnected. It
> can't be the voltage, because the voltage stays at 12 V (I measured it).
>
> The only explanation that comes to my mind is that the fan does not
> actually go to full speed even at full PWM duty cycle until it senses
> high temperature itself. This implies that the fan has some integrated
> temperature sensor.
>
> Is this possible? And if so, why would they do such a thing?
Yes, this is possible, I've seen this before.
Reason is that it allows for totally software and hardware agnostic fan
speed control. CPU safety is guaranteed by the fan itself and there is
no way to screw it (short of removing or under-powering the fan itself.)
Obviously the major drawback is that it takes control away from the
user, so I would stay away from such hardware if I can. But for lambda
users it makes some sense.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply
* Re: [Qemu-devel] [PATCH v2] realview: fix reset bit depending on platform
From: Peter Maydell @ 2011-11-06 18:44 UTC (permalink / raw)
To: Jean-Christophe DUBOIS; +Cc: qemu-devel, paul
In-Reply-To: <1320492237-3637-1-git-send-email-jcd@tribudubois.net>
On 5 November 2011 11:23, Jean-Christophe DUBOIS <jcd@tribudubois.net> wrote:
> Depending on the considered baseboard the bit used to
> reset the platform is different.
>
> Here is the list of considered Realview/Versatile platforms:
>
> Realview/Versatile AB for ARM926EJ-S: BOARD_ID = 0x100 = BOARD_ID_PB926
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0225d/CACCIFGI.html
>
> RealView Emulation Baseboard: BOARD_ID = 0x140 = BOARD_ID_EB
> No reset register
>
> RealView PB for ARM1176JZF-S: BOARD_ID = 0x147 = BOARD_ID_PB1176
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0425f/Caccifgi.html
>
> RealView PB for ARM11 MPCore: BOARD_ID = 0x159 = BOARD_ID_PB11MP
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0351e/CACCHBFB.html
>
> RealView PB for Cortex-A8: BOARD_ID = 0x178 = BOARD_ID_PBA8
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0417d/BBACIGAD.html
>
> RealView PB for Cortex-A9: BOARD_ID = 0x182 = BOARD_ID_PBX
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0440b/CACCHBFB.html
>
> Motherboard Express µATX: BOARD_ID = 0x190 = BOARD_ID_VEXPRESS
> No reset register
>
> v2:
> - Add multiple boards support
> - fix coding style
> - Added a BOARD_ID descriptor for unsupported baseboards.
>
> Signed-off-by: Jean-Christophe DUBOIS <jcd@tribudubois.net>
> ---
> hw/arm_sysctl.c | 43 ++++++++++++++++++++++++++++++++-----------
> 1 files changed, 32 insertions(+), 11 deletions(-)
I don't think you need to quote the URLs for every devboard TRM.
The 'v2/v3/etc' changes bit is better below the '---', ie not in
the final git commit message (people looking at git care only about
what the final patch does, not about what earlier versions failed
to do).
The Subject is kind of vague. Try:
"hw/arm_sysctl: Fix RESETCTL for realview-pb-a8 and -pbx-a9"
> diff --git a/hw/arm_sysctl.c b/hw/arm_sysctl.c
> index 17cf6f7..8f07fd5 100644
> --- a/hw/arm_sysctl.c
> +++ b/hw/arm_sysctl.c
> @@ -63,6 +63,8 @@ static const VMStateDescription vmstate_arm_sysctl = {
> */
> #define BOARD_ID_PB926 0x100
> #define BOARD_ID_EB 0x140
> +#define BOARD_ID_PB1176 0x147
> +#define BOARD_ID_PB11MP 0x159
We don't support these boards (and I see no reason why we ever should)
so there is no point adding these constants or any code to deal with them.
> @@ -143,7 +145,8 @@ static uint64_t arm_sysctl_read(void *opaque, target_phys_addr_t offset,
> case 0x58: /* BOOTCS */
> return 0;
> case 0x5c: /* 24MHz */
> - return muldiv64(qemu_get_clock_ns(vm_clock), 24000000, get_ticks_per_sec());
> + return muldiv64(qemu_get_clock_ns(vm_clock), 24000000,
> + get_ticks_per_sec());
> case 0x60: /* MISC */
> return 0;
> case 0x84: /* PROCID0 */
Please don't fix coding style problems in bits of the code the patch is
not touching anyway. (Also applies to a few other bits of the patch.)
The actual meat of the patch looks generally OK.
thanks
-- PMM
^ permalink raw reply
* Re: [PATCH] distclean: Remove generated .dtb files
From: Grant Likely @ 2011-11-06 18:42 UTC (permalink / raw)
To: Dirk Behme
Cc: Dirk Behme, linaro-dev-cunTk1MwBs8s++Sfvej+rw,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ, Jason Liu,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
grant.likely-QSEj5FYQhm4dnm+yROfE0A,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
In-Reply-To: <20111106183802.GB2546-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
On Sun, Nov 6, 2011 at 11:38 AM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
> On Sat, Nov 05, 2011 at 07:19:15AM +0100, Dirk Behme wrote:
>> The patch 'arm/dt: Add dtb make rule' adds support to
>> create a .dtb file. But this is never removed afterwards.
>> Remove the generated .dtb file if 'distclean' is called.
>>
>> Signed-off-by: Dirk Behme <dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
>> CC: Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
>> CC: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>> CC: Jason Liu <jason.hui-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>> CC: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
>
> Acked-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
... although why are only the .dtb files needed in the clean list?
How are the other built files cleaned? 'make clean' does remove the
other images, but I don't know what the mechanism is.
g.
>
>> ---
>> arch/arm/boot/Makefile | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile
>> index 1cd9b0a..08f0d35 100644
>> --- a/arch/arm/boot/Makefile
>> +++ b/arch/arm/boot/Makefile
>> @@ -71,6 +71,8 @@ $(obj)/%.dtb: $(src)/dts/%.dts
>>
>> $(obj)/dtbs: $(addprefix $(obj)/, $(dtb-y))
>>
>> +clean-files := *.dtb
>> +
>> quiet_cmd_uimage = UIMAGE $@
>> cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
>> -C none -a $(LOADADDR) -e $(STARTADDR) \
>> --
>> 1.7.0.4
>>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
^ permalink raw reply
* [PATCH] distclean: Remove generated .dtb files
From: Grant Likely @ 2011-11-06 18:42 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20111106183802.GB2546@ponder.secretlab.ca>
On Sun, Nov 6, 2011 at 11:38 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Sat, Nov 05, 2011 at 07:19:15AM +0100, Dirk Behme wrote:
>> The patch 'arm/dt: Add dtb make rule' adds support to
>> create a .dtb file. But this is never removed afterwards.
>> Remove the generated .dtb file if 'distclean' is called.
>>
>> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
>> CC: Rob Herring <rob.herring@calxeda.com>
>> CC: Shawn Guo <shawn.guo@freescale.com>
>> CC: Jason Liu <jason.hui@linaro.org>
>> CC: Grant Likely <grant.likely@secretlab.ca>
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
... although why are only the .dtb files needed in the clean list?
How are the other built files cleaned? 'make clean' does remove the
other images, but I don't know what the mechanism is.
g.
>
>> ---
>> ?arch/arm/boot/Makefile | ? ?2 ++
>> ?1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile
>> index 1cd9b0a..08f0d35 100644
>> --- a/arch/arm/boot/Makefile
>> +++ b/arch/arm/boot/Makefile
>> @@ -71,6 +71,8 @@ $(obj)/%.dtb: $(src)/dts/%.dts
>>
>> ?$(obj)/dtbs: $(addprefix $(obj)/, $(dtb-y))
>>
>> +clean-files := *.dtb
>> +
>> ?quiet_cmd_uimage = UIMAGE ?$@
>> ? ? ? ?cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
>> ? ? ? ? ? ? ? ? ?-C none -a $(LOADADDR) -e $(STARTADDR) \
>> --
>> 1.7.0.4
>>
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
^ permalink raw reply
* Re: [PATCH] agp: Enable all supported rates for graphic cards
From: Tormod Volden @ 2011-11-06 18:39 UTC (permalink / raw)
To: Corbin Simpson; +Cc: dri-devel
In-Reply-To: <CALiqSLcMVqMH4toUMhp+_O14mf2v02qUie7yYqfj-o4rScR=ng@mail.gmail.com>
On Sun, Nov 6, 2011 at 4:37 PM, Corbin Simpson
<mostawesomedude@gmail.com> wrote:
> Trusting the spec worries me; could this break anybody?
It will allow the user to override possibly safer default settings. If
a user has specified, say, 2x in his xorg.conf and this was not
honored because the card only reported 4x, this patch would finally
give him the 2x he is asking for. If 2x turns out to not work, he will
suddenly have problems. But the solution would be to fix his
xorg.conf. Up till now he might be thinking 2x works fine, while he
was actually getting another rate.
Generally, the default rate is defined by the DDX and the patch does
not change these policies. However, with the patch we may actually
apply the default value, instead of an undefined "0x" (i.e. the case
when the DDX sets 1x or 2x by default, but the card says only 4x). The
spec (I have checked section 6.1.10) does not say anything about
writing a zero rate, and I don't know what the silicon does. I don't
know of any way to read out the resulting speed. Is there any simple
agp benchmarking tools?
Of course, it would be good if more people who currently see "0x" in
dmesg would try this patch.
Note that Dave Jones did the same for bridges in
28af24bb8470c7d0573b703a2955548b73a6c066 to get rid of "0x" cases.
>
> Is there any reason to use the not-so-magic numbers instead of the named
> constants?
I followed the style of the surrounding code. I can follow up with a
patch using named constants everywhere if that would be desired.
Thanks for looking at it!
Tormod
>
> Sending from a mobile, pardon my terseness. ~ C.
>
> On Nov 6, 2011 7:03 AM, "Tormod Volden" <lists.tormod@gmail.com> wrote:
>>
>> From: Tormod Volden <debian.tormod@gmail.com>
>>
>> Some cards report that they support only 4x, in which case they
>> should support 2x and 1x as well, according to the AGP spec.
>>
>> Otherwise a requested 1x or 2x rate will result in 0 being set:
>>
>> agpgart-via 0000:00:00.0: putting AGP V2 device into 0x mode
>>
>> For instance ProSavage KN133 [5333:8d02] only reports 4x.
>>
>> Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
>> ---
>> drivers/char/agp/generic.c | 18 ++++++++++++++++++
>> 1 files changed, 18 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/char/agp/generic.c b/drivers/char/agp/generic.c
>> index b072648..c5d04e5 100644
>> --- a/drivers/char/agp/generic.c
>> +++ b/drivers/char/agp/generic.c
>> @@ -526,6 +526,24 @@ static void agp_v2_parse_one(u32 *requested_mode, u32
>> *bridge_agpstat, u32 *vga_
>> break;
>> }
>>
>> + /* Some graphic cards report they only support 4x, however the AGP
>> 2.0 spec
>> + * (section 4.1.1) says components must support the lower speeds
>> as well.
>> + */
>> + switch (*vga_agpstat & 7) {
>> + case 4:
>> + *vga_agpstat |= (AGPSTAT2_2X | AGPSTAT2_1X);
>> + printk(KERN_INFO PFX "Graphics card claims to only support
>> x4 rate. "
>> + "Fixing up support for x2 & x1\n");
>> + break;
>> + case 2:
>> + *vga_agpstat |= AGPSTAT2_1X;
>> + printk(KERN_INFO PFX "Graphics card claims to only support
>> x2 rate. "
>> + "Fixing up support for x1\n");
>> + break;
>> + default:
>> + break;
>> + }
>> +
>> /* Check the speed bits make sense. Only one should be set. */
>> tmp = *requested_mode & 7;
>> switch (tmp) {
>> --
>> 1.7.5.4
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
^ permalink raw reply
* [GIT PULL] Btrfs pull request
From: Chris Mason @ 2011-11-06 18:38 UTC (permalink / raw)
To: Linus Torvalds, linux-btrfs, LKML
Hi everyone,
This pull request is pretty beefy, it ended up merging a number of long
running projects and cleanup queues. I've got btrfs patches in the new
kernel.org btrfs repo. There are two different branches with the same
changes. for-linus is against 3.1 and has also been tested against
Linus' tree as of yesterday.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
The next-merged branch is the same btrfs code, but has a merge
commit for the current linux-next tree. There was only a single
conflict, linux-next has a fix for code that no longer exists, so the
merge is just to take my code. I know Linus won't end up using
this, it's just to demonstrate the conflict in case he ends up with that
patch.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git next-merged
The big features in this pull are:
Many cleanups and optimizations from Josef. Many of these fixup the
enospc throttling in btrfs, where we try to start IO to make sure we can
do all the allocations we've promised we'll do. The end result is a
dramatic improvement in random write workloads among many others.
Arne Jansen and Jan Schmidt have improved the scrubber and provided
utilities to walk btrfs' many backrefs. The scrubber is much faster
thanks to extensive btree readahead and instead of just telling you a
specific block is bad, it tells you which btree or which file was
impacted by that bad block.
There are also progs updates to give you the same backref walking from
the command line.
SUSE and Fujitsu have a nice set of error handling fixes, and Li Zefan
also closed out some problems in the mount -o autodefrag mode.
I kicked in an array of backup tree roots. If a given mount fails to go
through because a tree root is bad, you can mount -o recovery and it'll
walk through the array and try older versions of the FS.
I also spent a lot of time refining Fujitsu's log tree improvements.
This code has been around for quite a while, and I really wanted to get
it in this time. But yesterday I hit corruptions when I mixed heavy
fsyncs with heavy snapshotting, and I wasn't able to fix things in time
for this merge window.
Josef Bacik (60) commits (+1847/-1238):
Btrfs: don't check bytes_pinned to determine if we should commit the transaction (+0/-11)
Btrfs: allow callers to specify if flushing can occur for btrfs_block_rsv_check (+10/-10)
Btrfs: be smarter about committing the transaction in reserve_metadata_bytes (+67/-19)
Btrfs: release metadata from global reserve if we have to fallback for unlink (+4/-1)
Btrfs: wait for ordered extents if we're in trouble when shrinking delalloc (+17/-8)
Btrfs: add a io_ctl struct and helpers for dealing with the space cache (+375/-318)
Btrfs: seperate out btrfs_block_rsv_check out into 2 different functions (+37/-24)
Btrfs: check the return value of filemap_write_and_wait in the space cache (+5/-2)
Btrfs: don't increase the block_rsv's size when emergency allocating space (+0/-3)
Btrfs: use the global reserve when truncating the free space cache inode (+17/-5)
Btrfs: make sure to unset trans->block_rsv before running delayed refs (+11/-0)
Btrfs: only reserve space in fallocate if we have to do a preallocate (+16/-6)
Btrfs: stop passing a trans handle all around the reservation code (+39/-43)
Btrfs: skip looking for delalloc if we don't have ->fill_delalloc (+5/-1)
Btrfs: if we have a lot of pinned space, commit the transaction (+15/-0)
Btrfs: release trans metadata bytes before flushing delayed refs (+3/-8)
Btrfs: make a delayed_block_rsv for the delayed item insertion (+13/-7)
Btrfs: ratelimit the generation printk for the free space cache (+7/-5)
Btrfs: use the global reserve as a backup for deleting inodes (+11/-1)
Btrfs: allow shrink_delalloc flush the needed reclaimed pages (+3/-2)
Btrfs: only inherit btrfs specific flags when creating files (+11/-6)
Btrfs: break out of orphan cleanup if we can't make progress (+11/-0)
Btrfs: move stuff around in btrfs_inode to get better packing (+3/-3)
Btrfs: reserve some space for an orphan item when unlinking (+8/-1)
Btrfs: wait for ordered extents if we didn't reclaim enough (+1/-1)
Btrfs: check unused against how much space we actually want (+1/-1)
Btrfs: put the block group cache after we commit the super (+3/-3)
Btrfs: inline checksums into the disk free space cache (+172/-68)
Btrfs: use the inode's mapping mask for allocating pages (+18/-6)
Btrfs: fix space leak when we fail to make an allocation (+14/-6)
Btrfs: don't skip writing out a empty block groups cache (+6/-4)
Btrfs: use the transactions block_rsv for the csum root (+10/-6)
Btrfs: fix call to btrfs_search_slot in free space cache (+1/-1)
Btrfs: use d_obtain_alias when mounting subvol/subvolid (+1/-24)
Btrfs: allow us to overcommit our enospc reservations (+88/-18)
Btrfs: don't get the block_rsv in btrfs_free_tree_block (+0/-4)
Btrfs: handle enospc accounting for free space inodes (+47/-23)
Btrfs: reduce the amount of space needed for truncates (+15/-4)
Btrfs: kill the orphan space calculation for snapshots (+0/-90)
Btrfs: use bytes_may_use for all ENOSPC reservations (+112/-82)
Btrfs: optimize how we account for space in truncate (+29/-29)
Btrfs: fix how we reserve space for deleting inodes (+38/-11)
Btrfs: don't flush the cache inode before writing it (+0/-4)
Btrfs: take overflow into account in reserving space (+1/-1)
Btrfs: don't try to commit in btrfs_block_rsv_check (+4/-25)
Btrfs: fix the amount of space reserved for unlink (+10/-1)
Btrfs: fix regression in re-setting a large xattr (+11/-0)
Btrfs: introduce mount option no_space_cache (+22/-10)
Btrfs: delay iput when deleting a block group (+1/-1)
Btrfs: kill btrfs_truncate_reserve_metadata (+0/-34)
Btrfs: fix how we mount subvol=<whatever> (+135/-64)
Btrfs: calculate checksum space correctly (+118/-8)
Btrfs: kill the durable block rsv stuff (+17/-101)
Btrfs: fix delayed insertion reservation (+49/-8)
Btrfs: fix orphan cleanup regression (+17/-19)
Btrfs: kill unused parts of block_rsv (+6/-22)
Btrfs: introduce convert_extent_bit (+190/-0)
Btrfs: set truncate block rsv's size (+2/-0)
Btrfs: kill reserved_bytes in inode (+0/-8)
Btrfs: stop using write_one_page (+20/-67)
Jan Schmidt (13) commits (+1954/-303):
btrfs: new ioctls to do logical->inode and inode->path resolving (+162/-0)
btrfs scrub: add fixup code for errors on nodatasum files (+183/-6)
btrfs: integrating raid-repair and scrub-fixup-nodatasum (+67/-25)
btrfs: Moved repair code from inode.c to extent_io.c (+393/-159)
btrfs: added helper functions to iterate backrefs (+851/-1)
btrfs: btrfs_multi_bio replaced with btrfs_bio (+90/-78)
btrfs: Do not use bio->bi_bdev after submission (+1/-1)
btrfs: add mirror_num to extent_read_full_page (+6/-6)
btrfs scrub: print paths of corrupted files (+163/-6)
btrfs scrub: use int for mirror_num, not u64 (+4/-4)
btrfs scrub: bugfix: mirror_num off by one (+6/-6)
btrfs scrub: added unverified_errors (+26/-11)
btrfs: Put mirror_num in bi_bdev (+2/-0)
Chris Mason (10) commits (+490/-67):
Btrfs: make sure to flush queued bios if write_cache_pages waits (+22/-10)
Btrfs: don't wait as long for more batches during SSD log commit (+2/-2)
Btrfs: fix extent_buffer leak in the metadata IO error handling (+1/-0)
Btrfs: ClearPageError during writepage and clean_tree_block (+10/-1)
Btrfs: make sure btrfs_remove_free_space doesn't leak EAGAIN (+3/-1)
Btrfs: fix the new inspection ioctls for 32 bit compat (+15/-16)
Btrfs: stop the readahead threads on failed mount (+1/-0)
Btrfs: fix extent pinning bugs in the tree log (+59/-8)
Btrfs: fix race during transaction joins (+8/-5)
Btrfs: add a log of past tree roots (+369/-24)
Li Zefan (7) commits (+47/-24):
Btrfs: fix wrong max_to_defrag in btrfs_defrag_file() (+1/-1)
Btrfs: honor extent thresh during defragmentation (+26/-11)
Btrfs: remove BUG_ON() in compress_file_range() (+5/-1)
Btrfs: use i_size_read() in btrfs_defrag_file() (+4/-3)
Btrfs: fix defragmentation regression (+4/-2)
Btrfs: fix direct-io vs nodatacow (+1/-2)
Btrfs: fix array bound checking (+6/-4)
Ilya Dryomov (6) commits (+22/-21):
Btrfs: pass the correct root to lookup_free_space_inode() (+1/-1)
Btrfs: rename btrfs_bio multi -> bbio for consistency (+15/-15)
Btrfs: fix a potential btrfs_bio leak on scrub fixups (+1/-0)
Btrfs: stop leaking btrfs_bios on readahead (+2/-0)
Btrfs: fix a bug when opening seed devices (+1/-1)
Btrfs: close all bdevs on mount failure (+2/-4)
Arne Jansen (6) commits (+1130/-70):
btrfs: add an extra wait mode to read_extent_buffer_pages (+9/-6)
btrfs: initial readahead code and prototypes (+967/-1)
btrfs: add READAHEAD extent buffer flag (+35/-0)
btrfs: state information for readahead (+31/-0)
btrfs: use readahead API for scrub (+50/-62)
btrfs: hooks for readahead (+38/-1)
David Sterba (3) commits (+105/-77):
btrfs: do not allow mounting non-subvolumes via subvol option (+19/-0)
btrfs: separate superblock items out of fs_info (+78/-76)
btrfs: ratelimit WARN_ON in use_block_rsv (+8/-1)
Zheng Yan (1) commits (+4/-1):
btrfs: check file extent backref offset underflow
Lukas Czerner (1) commits (+5/-1):
btrfs: return EINVAL if start > total_bytes in fitrim ioctl
Daniel J Blueman (1) commits (+6/-2):
btrfs: fix oops on failure path
Liu Bo (1) commits (+1/-1):
Btrfs: do not set EXTENT_DIRTY along with EXTENT_DELALLOC
Diego Calleja (1) commits (+1/-3):
btrfs: fix memory leak in btrfs_defrag_file
Jeff Liu (1) commits (+8/-2):
btrfs: trivial fix, a potential memory leak in btrfs_parse_early_options()
Miao Xie (1) commits (+7/-0):
Btrfs: fix race between multi-task space allocation and caching space
Tsutomu Itoh (1) commits (+7/-10):
Btrfs: fix return value of btrfs_get_acl()
Total: (113) commits
fs/btrfs/Makefile | 3 +-
fs/btrfs/acl.c | 17 +-
fs/btrfs/backref.c | 776 +++++++++++++++++++++++++++++++++++
fs/btrfs/backref.h | 62 +++
fs/btrfs/btrfs_inode.h | 17 +-
fs/btrfs/compression.c | 3 +-
fs/btrfs/ctree.c | 10 +-
fs/btrfs/ctree.h | 198 ++++++++--
fs/btrfs/delayed-inode.c | 50 ++-
fs/btrfs/disk-io.c | 434 +++++++++++++++++---
fs/btrfs/disk-io.h | 4 +-
fs/btrfs/extent-tree.c | 848 +++++++++++++++++++++++---------------
fs/btrfs/extent_io.c | 614 +++++++++++++++++++++++++++-
fs/btrfs/extent_io.h | 23 +-
fs/btrfs/file-item.c | 17 +-
fs/btrfs/file.c | 25 +-
fs/btrfs/free-space-cache.c | 926 +++++++++++++++++++++++++----------------
fs/btrfs/inode-map.c | 6 +-
fs/btrfs/inode.c | 457 +++++++--------------
fs/btrfs/ioctl.c | 227 +++++++++--
fs/btrfs/ioctl.h | 29 ++
fs/btrfs/print-tree.c | 8 +-
fs/btrfs/reada.c | 951 +++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/relocation.c | 24 +-
fs/btrfs/scrub.c | 591 ++++++++++++++++++++++-----
fs/btrfs/super.c | 298 +++++++++-----
fs/btrfs/transaction.c | 146 +++----
fs/btrfs/tree-log.c | 19 +-
fs/btrfs/volumes.c | 207 ++++++----
fs/btrfs/volumes.h | 18 +-
fs/btrfs/xattr.c | 11 +
31 files changed, 5416 insertions(+), 1603 deletions(-)
^ permalink raw reply
* Re: [PATCH] distclean: Remove generated .dtb files
From: Grant Likely @ 2011-11-06 18:38 UTC (permalink / raw)
To: Dirk Behme
Cc: Dirk Behme, linaro-dev-cunTk1MwBs8s++Sfvej+rw,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ, Jason Liu,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
grant.likely-QSEj5FYQhm4dnm+yROfE0A,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
In-Reply-To: <1320473955-4500-1-git-send-email-dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
On Sat, Nov 05, 2011 at 07:19:15AM +0100, Dirk Behme wrote:
> The patch 'arm/dt: Add dtb make rule' adds support to
> create a .dtb file. But this is never removed afterwards.
> Remove the generated .dtb file if 'distclean' is called.
>
> Signed-off-by: Dirk Behme <dirk.behme-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
> CC: Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
> CC: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> CC: Jason Liu <jason.hui-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> CC: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Acked-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
> ---
> arch/arm/boot/Makefile | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile
> index 1cd9b0a..08f0d35 100644
> --- a/arch/arm/boot/Makefile
> +++ b/arch/arm/boot/Makefile
> @@ -71,6 +71,8 @@ $(obj)/%.dtb: $(src)/dts/%.dts
>
> $(obj)/dtbs: $(addprefix $(obj)/, $(dtb-y))
>
> +clean-files := *.dtb
> +
> quiet_cmd_uimage = UIMAGE $@
> cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
> -C none -a $(LOADADDR) -e $(STARTADDR) \
> --
> 1.7.0.4
>
^ permalink raw reply
* [PATCH] distclean: Remove generated .dtb files
From: Grant Likely @ 2011-11-06 18:38 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1320473955-4500-1-git-send-email-dirk.behme@de.bosch.com>
On Sat, Nov 05, 2011 at 07:19:15AM +0100, Dirk Behme wrote:
> The patch 'arm/dt: Add dtb make rule' adds support to
> create a .dtb file. But this is never removed afterwards.
> Remove the generated .dtb file if 'distclean' is called.
>
> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
> CC: Rob Herring <rob.herring@calxeda.com>
> CC: Shawn Guo <shawn.guo@freescale.com>
> CC: Jason Liu <jason.hui@linaro.org>
> CC: Grant Likely <grant.likely@secretlab.ca>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
> ---
> arch/arm/boot/Makefile | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/boot/Makefile b/arch/arm/boot/Makefile
> index 1cd9b0a..08f0d35 100644
> --- a/arch/arm/boot/Makefile
> +++ b/arch/arm/boot/Makefile
> @@ -71,6 +71,8 @@ $(obj)/%.dtb: $(src)/dts/%.dts
>
> $(obj)/dtbs: $(addprefix $(obj)/, $(dtb-y))
>
> +clean-files := *.dtb
> +
> quiet_cmd_uimage = UIMAGE $@
> cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
> -C none -a $(LOADADDR) -e $(STARTADDR) \
> --
> 1.7.0.4
>
^ permalink raw reply
* Re: [PATCH 1/3] apply: get rid of useless x < 0 comparison on a size_t type
From: Junio C Hamano @ 2011-11-06 18:35 UTC (permalink / raw)
To: Ævar Arnfjörð Bjarmason, Giuseppe Bilotta
Cc: git, Jim Meyering, Fredrik Gustafsson
In-Reply-To: <1320581184-4557-2-git-send-email-avarab@gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> According to the C standard size_t is always unsigned, therefore the
> comparison "n1 < 0 || n2 < 0" when n1 and n2 are size_t will always be
> false.
>
> This was raised by clang 2.9 which throws this warning when compiling
> apply.c:
>
> builtin/apply.c:253:9: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
> if (n1 < 0 || n2 < 0)
> ~~ ^ ~
> builtin/apply.c:253:19: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare]
> if (n1 < 0 || n2 < 0)
> ~~ ^ ~
>
> This check was originally added in v1.6.5-rc0~53^2 by Giuseppe Bilotta
> while adding an option to git-apply to ignore whitespace differences.
>
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> ---
I agree that these quantities can never be negative, so I'll apply the
patch as is.
But I have this suspicion that this was a rather sloppy defensive check to
protect this codepath against potential breakage in another codepath (most
likely update_pre_post_images() touched by the same patch) that adjusts
image->line[].len the caller of this function uses to feed these two
parameters. Giuseppe may have been not confident enough that the code
added to that function ensures not to undershoot when it reduces "len", or
something.
Giuseppe, can you explain what is going on?
Thanks
> builtin/apply.c | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/builtin/apply.c b/builtin/apply.c
> index 84a8a0b..b3b59db 100644
> --- a/builtin/apply.c
> +++ b/builtin/apply.c
> @@ -250,9 +250,6 @@ static int fuzzy_matchlines(const char *s1, size_t n1,
> const char *last2 = s2 + n2 - 1;
> int result = 0;
>
> - if (n1 < 0 || n2 < 0)
> - return 0;
> -
> /* ignore line endings */
> while ((*last1 == '\r') || (*last1 == '\n'))
> last1--;
^ permalink raw reply
* [PATCH] usbnet: fix oops in usbnet_start_xmit
From: Konstantin Khlebnikov @ 2011-11-06 19:33 UTC (permalink / raw)
To: Oliver Neukum; +Cc: netdev, David S. Miller, devel, Michael Riesch
This patch fixes the bug added in commit v3.1-rc7-1055-gf9b491e
SKB can be NULL at this point, at least for cdc-ncm.
Let's call skb_tx_timestamp() after driver specific tx-fixup hacks.
Signed-off-by: Konstantin Khlebnikov <khlebnikov@openvz.org>
---
drivers/net/usb/usbnet.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c
index 7d60821..485be70 100644
--- a/drivers/net/usb/usbnet.c
+++ b/drivers/net/usb/usbnet.c
@@ -1057,8 +1057,6 @@ netdev_tx_t usbnet_start_xmit (struct sk_buff *skb,
unsigned long flags;
int retval;
- skb_tx_timestamp(skb);
-
// some devices want funky USB-level framing, for
// win32 driver (usually) and/or hardware quirks
if (info->tx_fixup) {
@@ -1075,6 +1073,8 @@ netdev_tx_t usbnet_start_xmit (struct sk_buff *skb,
}
length = skb->len;
+ skb_tx_timestamp(skb);
+
if (!(urb = usb_alloc_urb (0, GFP_ATOMIC))) {
netif_dbg(dev, tx_err, dev->net, "no urb\n");
goto drop;
^ permalink raw reply related
* Re: [PATCH 1/2] gpiolib: output basic details and consolidate gpio device drivers
From: Grant Likely @ 2011-11-06 18:33 UTC (permalink / raw)
To: Hartmut Knaack; +Cc: linux-kernel
In-Reply-To: <4EB5AA57.7070008@gmx.de>
On Sat, Nov 05, 2011 at 10:27:51PM +0100, Hartmut Knaack wrote:
> This patch adds a kernel message, containing GPIO range and device name on successful device registration.
>
> Signed-off-by: Hartmut Knaack <knaack.h@gmx.de>
> -------------------------------------------------------------
For next time; the divider between commit text and patch must be
exactly 3 '-' characters long, no more, no less. Otherwise the tools
don't handle it properly.
> diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> index a971e3d..d919ac6 100644
> --- a/drivers/gpio/gpiolib.c
> +++ b/drivers/gpio/gpiolib.c
> @@ -1088,6 +1088,10 @@ unlock:
> status = gpiochip_export(chip);
> if (status)
> goto fail;
> +
Whitespace error.
Otherwise looks good. I'm picking it up and squashing it together
with the second patch.
> + pr_info("gpiochip_add: registered GPIOs %d to %d on device: %s\n",
> + chip->base, chip->base + chip->ngpio - 1,
> + chip->label ? : "generic");
>
> return 0;
> fail:
>
^ permalink raw reply
* Re: [Xenomai-help] Xenomai 2.6.0 - kernel seg faults on AT91
From: Gilles Chanteperdrix @ 2011-11-06 18:32 UTC (permalink / raw)
To: at91_enthus; +Cc: xenomai
In-Reply-To: <4EB6D11A.6070008@domain.hid>
On 11/06/2011 07:25 PM, at91_enthus wrote:
> On 11/06/2011 12:10 PM, at91_enthus wrote:
>> On 11/06/2011 12:01 PM, Gilles Chanteperdrix wrote:
>>> On 11/06/2011 06:56 PM, at91_enthus wrote:
>>>> Hi.
>>>>
>>>> I gave Xenomai 2.6.0 a try and installed a newly patched kernel on my
>>>> AT91SAM9G20 board.
>>>>
>>>> Here is my setup:
>>>>
>>>> proc: AT91SAM9G20
>>>> kernel: 2.6.35.9
>>>> OS: embedded Debian Squeeze
>>>>
>>>> The board boots fine up to stage 2 (user terminal). Sometimes, I am able
>>>> to get a login terminal, despite seg fault messages.
>>>>
>>>> A similar behavior occurs in a Xenomai capable 2.6.37 kernel, only
>>>> without the fault messages. In this case the board simply freezes.
>>>>
>>>> I included the files (.config and fault messages) in the attachments.
>>>>
>>> You enabled CONFIG_FCSE_GUARANTEED, I do not think Debian squeeze can
>>> boot with that, you need a real embedded filesystem, or use
>>> CONFIG_FCSE_BEST_EFFORT.
>>>
>>>
>> Since I've started looking in to Xenomai, I have been using FCSE
>> "guaranteed" and "best efort" along with both Debian Squeeze and Lenny
>> (Xenomai 2.5 series) without any issues.
>>
>> I'll change the FCSE setting to see if I get a different behavior.
>>
>> Regards.
>
> I put the results for CONFIG_FCSE_BEST_EFFORT in the attachment.
Unusable. To make it usable, the following options are lacking:
CONFIG_FCSE_MESSAGES
CONFIG_FRAME_POINTER
CONFIG_DEBUG_USER
CONFIG_DEBUG_ERRORS
And add debug_user=29 on the command line.
--
Gilles.
^ permalink raw reply
* Re: [Qemu-devel] [PATCH] KVM: Add wrapper script around QEMU to test kernels
From: Ted Ts'o @ 2011-11-06 18:31 UTC (permalink / raw)
To: Anthony Liguori
Cc: Blue Swirl, kvm@vger.kernel.org list,
linux-kernel@vger.kernel.org List, Alexander Graf,
qemu-devel Developers, Pekka Enberg, Avi Kivity,
Américo Wang, Ingo Molnar, Linus Torvalds
In-Reply-To: <4EB6BEFA.6000303@codemonkey.ws>
On Sun, Nov 06, 2011 at 11:08:10AM -0600, Anthony Liguori wrote:
> I'm quite happy with KVM tool and hope they continue working on it.
> My only real wish is that they wouldn't copy QEMU so much and would
> try bolder things that are fundamentally different from QEMU.
My big wish is that they don't try to merge the KVM tool into the
kernel code. It's a separate userspace project, and there's no reason
for it to be bundled with kernel code. It just makes the kernel
sources larger. The mere fact that qemu-kvm exists means that the KVM
interface has to remain backward compatible; it *is* an ABI.
So integrating kvm-tool into the kernel isn't going to work as a free
pass to make non-backwards compatible changes to the KVM user/kernel
interface. Given that, why bloat the kernel source tree size?
Please, keep the kvm-tool sources as a separate git tree.
- Ted
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.