Hi all,
Changes since next-20080611:
Dropped trees (temporary): ldp (it is unfetchable - probably something to
do with the new Staging tree), block (it just has too many conflicts and
breaks the powerpc build).
A few patches were removed from the driver-core tree which means some
conflicts with other trees have gone.
The pci tree lost two conflict with the driver-core tree.
The acpi tree gained a trivial conflict with the cpus4096 tree.
The powerpc tree lost seven conflicts with the driver-core tree.
The mmc tree lost its conflict with the driver-core tree.
The firmware tree gained a conflict with the bkl-removal tree. It also
required a build fix patch.
I have applied the following temporary patch for known build problems:
"Fix various 8390 builds" - the net tree broke builds on various
architectures - hopefully this patch will go into the net tree shortly.
"Revert "kbuild: simplify vmlinux link stage"" - this fixed the
powerpc allyesconfig and sparc32 defconfig builds.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups, it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig and i386, sparc and sparc64 defconfig.
Below is a summary of the state of the merge.
We are up to 90 trees (counting Linus' and 13 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell [email protected]
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging powerpc-merge/merge
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sparc-current/master
Merging sound-current/for-linus
Merging arm-current/master
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging quilt/driver-core
Merging quilt/usb
Merging tip-core/auto-core-next
Merging cpus4096/auto-cpus4096-next
Merging ftrace/auto-ftrace-next
Merging genirq/auto-genirq-next
Merging safe-poison-pointers/auto-safe-poison-pointers-next
Merging sched/auto-sched-next
CONFLICT (content): Merge conflict in kernel/Makefile
Applying ftrace: fix rculist split fallout
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
Merging x86/auto-x86-next
CONFLICT (content): Merge conflict in arch/x86/kernel/process_32.c
CONFLICT (content): Merge conflict in arch/x86/kernel/process_64.c
Merging pci/linux-next
CONFLICT (content): Merge conflict in arch/x86/pci/irq.c
CONFLICT (content): Merge conflict in include/linux/device.h
Merging quilt/device-mapper
Merging hid/mm
Merging quilt/i2c
CONFLICT (content): Merge conflict in drivers/i2c/i2c-core.c
Merging quilt/kernel-doc
Merging avr32/avr32-arch
Merging v4l-dvb/stable
Merging s390/features
CONFLICT (content): Merge conflict in drivers/s390/block/dasd.c
CONFLICT (content): Merge conflict in drivers/s390/block/dasd_eckd.c
CONFLICT (content): Merge conflict in drivers/s390/block/dasd_fba.c
CONFLICT (content): Merge conflict in drivers/s390/char/tape_core.c
CONFLICT (content): Merge conflict in drivers/s390/cio/device_fsm.c
CONFLICT (content): Merge conflict in drivers/s390/net/claw.c
CONFLICT (content): Merge conflict in drivers/s390/net/ctcm_main.c
CONFLICT (content): Merge conflict in drivers/s390/net/lcs.c
Merging sh/master
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
Merging infiniband/for-next
Merging acpi/test
CONFLICT (content): Merge conflict in drivers/acpi/processor_throttling.c
Merging blackfin/for-linus
Merging nfsd/nfsd-next
CONFLICT (content): Merge conflict in net/sunrpc/svc.c
Merging ieee1394/for-next
Merging hwmon/testing
Merging ubi/master
Merging kvm/master
Merging dlm/next
Merging scsi/master
Applying scsi: fix fallout from the class_find_device API change
Applying scsi: fix fallout from KOBJ_NAME_LEN removal
Merging ia64/test
Merging tests/master
CONFLICT (content): Merge conflict in lib/Kconfig.debug
Merging ocfs2/linux-next
Merging selinux/for-akpm
Merging quilt/m68k
Merging powerpc/powerpc-next
Merging lblnet/master
Merging ext4/next
Merging 4xx/next
Merging async_tx/next
Merging udf/for_next
Merging security-testing/next
Merging net/master
CONFLICT (content): Merge conflict in Documentation/powerpc/booting-without-of.txt
Merging sparc/master
Merging galak/powerpc-next
CONFLICT (content): Merge conflict in Documentation/powerpc/booting-without-of.txt
Merging mtd/master
CONFLICT (content): Merge conflict in include/asm-avr32/arch-at32ap/board.h
Merging wireless/master
Merging crypto/master
Merging vfs/vfs-2.6.25
Merging sound/master
Merging arm/devel
CONFLICT (content): Merge conflict in arch/arm/mach-at91/board-yl-9200.c
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/tosa.c
Merging cpufreq/next
CONFLICT (content): Merge conflict in drivers/cpufreq/cpufreq.c
Merging v9fs/for-next
Merging quilt/rr
CONFLICT (content): Merge conflict in drivers/net/virtio_net.c
Merging cifs/master
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging semaphore-removal/semaphore-removal
CONFLICT (content): Merge conflict in drivers/net/ps3_gelic_wireless.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_attr.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_def.h
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_mbx.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_mid.c
CONFLICT (content): Merge conflict in drivers/scsi/qla2xxx/qla_os.c
Merging bkl-removal/bkl-removal
Merging trivial/next
Merging ubifs/for_andrew
Merging lsm/for-next
Merging embedded/master
Merging firmware/master
CONFLICT (content): Merge conflict in drivers/char/ip2/ip2main.c
CONFLICT (content): Merge conflict in drivers/usb/misc/isight_firmware.c
CONFLICT (content): Merge conflict in drivers/usb/serial/Kconfig
CONFLICT (delete/modify): drivers/usb/serial/ti_fw_3410.h deleted in firmware/master and modified in HEAD. Version HEAD of drivers/usb/serial/ti_fw_3410.h left in tree.
CONFLICT (delete/modify): drivers/usb/serial/ti_fw_5052.h deleted in firmware/master and modified in HEAD. Version HEAD of drivers/usb/serial/ti_fw_5052.h left in tree.
CONFLICT (content): Merge conflict in drivers/usb/serial/ti_usb_3410_5052.c
CONFLICT (content): Merge conflict in sound/pci/Kconfig
CONFLICT (content): Merge conflict in sound/pci/maestro3.c
CONFLICT (content): Merge conflict in sound/pci/ymfpci/ymfpci_main.c
Applying firmware: fix ip2 conversion fallout
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
CONFLICT (content): Merge conflict in drivers/video/backlight/Kconfig
CONFLICT (content): Merge conflict in drivers/video/backlight/Makefile
Applying Fix various 8390 builds
Created commit 2eaed86: Revert "kbuild: simplify vmlinux link stage"
Am Donnerstag, den 12.06.2008, 17:53 +1000 schrieb Stephen Rothwell:
> Changes since next-20080611:
>
Beginning with next-20080612 i've got no sound!
git bisect told me that, the offending commit is cbc5a5b7d12b4d461bff132f76abc0d4f9f3d8fc (ALSA: hda - Add bdl_pos_adj option):
I need to add the option bdl_pos_adj=0, to make sound work again, which gives this dmesg entry:
[ 64.697747] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
The sound card is:
$ cat /proc/asound/cards
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfbff0000 irq 21
$ /sbin/lspci -vv -s 00:06.1
00:06.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2)
Subsystem: Micro-Star International Co., Ltd. Unknown device 7250
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin B routed to IRQ 21
Region 0: Memory at fbff0000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
What makes me wonder is, that the commit says:
" The new option adds the size of the delay in frames. As default,
it's set to 1 -- that is, one sample delay. Even the hardware is
really correct, one sample delay is relatively harmless in comparison
with reporting wrong positions."
Maybe my definition of "harmless" is not "no sound".
Would you please check this problem?
greets
thomas
At Fri, 13 Jun 2008 21:56:31 +0200,
Thomas Meyer wrote:
>
> Am Donnerstag, den 12.06.2008, 17:53 +1000 schrieb Stephen Rothwell:
>
> > Changes since next-20080611:
> >
>
> Beginning with next-20080612 i've got no sound!
>
> git bisect told me that, the offending commit is cbc5a5b7d12b4d461bff132f76abc0d4f9f3d8fc (ALSA: hda - Add bdl_pos_adj option):
>
> I need to add the option bdl_pos_adj=0, to make sound work again, which gives this dmesg entry:
>
> [ 64.697747] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
>
> The sound card is:
>
> $ cat /proc/asound/cards
> 0 [NVidia ]: HDA-Intel - HDA NVidia
> HDA NVidia at 0xfbff0000 irq 21
>
>
> $ /sbin/lspci -vv -s 00:06.1
> 00:06.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2)
> Subsystem: Micro-Star International Co., Ltd. Unknown device 7250
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0 (500ns min, 1250ns max)
> Interrupt: pin B routed to IRQ 21
> Region 0: Memory at fbff0000 (32-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: HDA Intel
> Kernel modules: snd-hda-intel
>
> What makes me wonder is, that the commit says:
> " The new option adds the size of the delay in frames. As default,
> it's set to 1 -- that is, one sample delay. Even the hardware is
> really correct, one sample delay is relatively harmless in comparison
> with reporting wrong positions."
>
> Maybe my definition of "harmless" is not "no sound".
> Would you please check this problem?
It was harmless for Intel and ATI hardwares :)
We've not tested NVidia ones. Good that you caught it fast.
Could you check whether another value, e.g. bdl_pos_adj=32 works?
Since the warning is shown with bdl_pos_adj=0, any position adjustment
is necessary, but likely Nvidia hardware doesn't allow such a fine
sample resolution like bdl_pos_adj=1.
Thanks,
Takashi
Zitat von Takashi Iwai <[email protected]>:
> It was harmless for Intel and ATI hardwares :)
> We've not tested NVidia ones. Good that you caught it fast.
>
> Could you check whether another value, e.g. bdl_pos_adj=32 works?
Yes, indeed. bdl_pos_adj=32 works, too.
Thanks for the quick response.
greets
thomas
At Fri, 13 Jun 2008 20:39:27 +0200,
Thomas Meyer wrote:
>
> Zitat von Takashi Iwai <[email protected]>:
>
> > It was harmless for Intel and ATI hardwares :)
> > We've not tested NVidia ones. Good that you caught it fast.
> >
> > Could you check whether another value, e.g. bdl_pos_adj=32 works?
>
> Yes, indeed. bdl_pos_adj=32 works, too.
>
> Thanks for the quick response.
Thanks for a quick check!
Looks like bdl_pos_adj=32 except for Intel is safer.
I'll fix it now.
Takashi