IA64 ATA patch.
We've had this in Fedora since 2007/02/27
Can anyone recall why? and more importantly, why it isn't upstream?
Dave
--- linux-2.6.20/arch/ia64/kernel/quirks.c 1969-12-31 19:00:00.0
-0500
+++ linux-2.6.20_fix/arch/ia64/kernel/quirks.c 2007-02-13 13:56:34.0
-0500
@@ -0,0 +1,45 @@
+/*
+ * This file contains work-arounds for ia64 platform bugs.
+ */
+#include linux/pci.h
+
+/*
+ * quirk_intel_ide_controller: If an ide/ata controller is
+ * at legacy mode, BIOS might initiates BAR(bar 0~3 and 5)
+ * with incorrect value. This quirk will reset the incorrect
+ * value to 0.
+ */
+static void __devinit quirk_intel_ide_controller(struct pci_dev *dev)
+{
+ unsigned int pos;
+ struct resource *res;
+ int fixed = 0;
+ u8 tmp8;
+
+ if ((dev-class 8) != PCI_CLASS_STORAGE_IDE)
+ return;
+
+ /* TODO: What if one channel is in native mode ... */
+ pci_read_config_byte(dev, PCI_CLASS_PROG, tmp8);
+ if ((tmp8 5) == 5)
+ return;
+
+ for( pos = 0; pos 6; pos ++ ) {
+ res = dev-resource[pos];
+ if (!(res-flags (IORESOURCE_IO | IORESOURCE_MEM)))
+ continue;
+
+ if (!res-start res-end) {
+ res-start = res-end = 0;
+ res-flags = 0;
+ fixed = 1;
+ }
+ }
+ if (fixed)
+ printk(KERN_WARNING
+ PCI device %s: BIOS resource configuration fixed.\n,
+ pci_name(dev));
+}
+
+DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801DB_11,
quirk_intel_ide_controller);
+
--- linux-2.6.21.noarch/arch/ia64/kernel/Makefile~ 2007-05-27
23:23:36.0 -0400
+++ linux-2.6.21.noarch/arch/ia64/kernel/Makefile 2007-05-27
23:23:48.0 -0400
@@ -33,6 +33,7 @@ obj-$(CONFIG_CRASH_DUMP) += crash_dump.o
obj-$(CONFIG_IA64_UNCACHED_ALLOCATOR) += uncached.o
obj-$(CONFIG_AUDIT)+= audit.o
obj-$(CONFIG_PCI_MSI) += msi_ia64.o
+obj-$(CONFIG_PCI) += quirks.o
mca_recovery-y += mca_drv.o mca_drv_asm.o
obj-$(CONFIG_IA64_MC_ERR_INJECT)+= err_inject.o
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
rawhide patches.
I just sifted through what we had in rawhide, after noticing that ls *.patch was starting to scroll my terminal (which is never a good sign). In doing so, I found a bunch of patches that weren't applied any more that we forgot to remove, and a bunch that were applied that shouldn't have been. Sifting through the remnants gave me a list that I've added to cvs as the file 'TODO' in devel. Hopefully we can keep this up to date as patches are introduced/removed. At the least it should serve as reasoning for why the hell we're carrying some patches for years (some of the CVS changelogs are pretty crappy, including some from yours truly). Here's what it looks like today.. Dave drm-modesetting-i915.patch drm-modesetting-radeon.patch linux-2.6-export-shmem-bits-for-gem.patch Intel/Radeon kernel mode-setting. Won't go upstream for a while. drm-nouveau.patch Nouveau DRM driver. Won't go upstream until ABI confirmed. linux-2.6-acpi-clear-wake-status.patch linux-2.6-acpi-video-dos.patch linux-2.6-defaults-acpi-video.patch linux-2.6-input-dell-keyboard-keyup.patch linux-2.6-eeepc-laptop-update.patch mjg59 ACPI/laptop bits. Upstreamable for 2.6.28 ? linux-2.6-at76.patch linux-2.6-iwlwifi-use-dma_alloc_coherent.patch linux-2.6-wireless.patch linux-2.6-wireless-pending.patch Linville. Wireless bits. Most should be upstream for 2.6.28 linux-2.6-ata-quirk.patch IA64 oddness. Query sent to f-k-l linux-2.6-build-nonintconfig.patch linux-2.6-debug-nmi-timeout.patch linux-2.6-debug-spinlock-taint.patch linux-2.6-debug-taint-vm.patch linux-2.6-debug-vm-would-have-oomkilled.patch linux-2.6-scsi-cpqarray-set-master.patch linux-2.6-usb-ehci-hcd-respect-nousb.patch Push for 2.6.28 linux-2.6-compile-fixes.patch linux-2.6-hotfixes.patch Empty linux-2.6-crash-driver.patch Not upstreamable. linux-2.6-debug-always-inline-kzalloc.patch Sent upstream Sep 25 2008 linux-2.6-debug-sizeof-structs.patch Fedora local debug stuff. linux-2.6-default-mmf_dump_elf_headers.patch linux-2.6-utrace.patch linux-2.6-x86-tracehook.patch Roland magick utrace linux-2.6-defaults-fat-utf8.patch Drop? linux-2.6-defaults-pci_no_msi.patch linux-2.6-input-kill-stupid-messages.patch linux-2.6-x86-tune-generic.patch Fedora local choices uninteresting to upstream linux-2.6-e1000e-add-support-for-82567LM-3-and-82567LF-3-ICH10D-parts.patch linux-2.6-e1000e-add-support-for-new-82574L-part.patch linux-2.6-e1000e-add-support-for-the-82567LM-4-device.patch linux-2.6-e1000-ich9.patch linux-2.6-firewire-git-update.patch linux-2.6-netdev-atl2.patch Should go upstream for .28 linux-2.6-efika-not-chrp.patch linux-2.6-g5-therm-shutdown.patch linux-2.6-imac-transparent-bridge.patch linux-2.6-ps3-ehci-iso.patch linux-2.6-ps3-legacy-bootloader-hack.patch linux-2.6-ps3-storage-alias.patch linux-2.6-vio-modalias.patch ppc bits. dwmw2. linux-2.6-execshield.patch linux-2.6-xen-execshield-add-xen-specific-load_user_cs_desc.patch linux-2.6-xen-execshield-fix-endless-gpf-fault-loop.patch linux-2.6-xen-execshield-only-define-load_user_cs_desc-on-32-bit.patch Not interesting to upstream. linux-2.6-lirc.patch jarod working on upstreaming linux-2.6-merge-efifb-imacfb.patch pjones. merge for 2.6.28 ? linux-2.6-nfs-client-mounts-hang.patch SteveD. Sent ping on Sep 25 to find out status. linux-2.6-net-silence-noisy-printks.patch linux-2.6-piix3-silence-quirk.patch linux-2.6-quiet-iommu.patch linux-2.6-silence-acpi-blacklist.patch linux-2.6-silence-fbcon-logo.patch linux-2.6-silence-noise.patch Fedora local 'hush' patches. linux-2.6-selinux-mprotect-checks.patch linux-2.6-sparc-selinux-mprotect-checks.patch Not upstreamable. linux-2.6-serial-460800.patch Probably not upstreamable. http://marc.theaimsgroup.com/?l=linux-kernelm=112687270832687w=2 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126403 http://lkml.org/lkml/2006/8/2/208 linux-2.6-squashfs.patch Sigh. Who the hell knows when this will go upstream. linux-2.6-sysrq-c.patch Que? -- http://www.codemonkey.org.uk ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: rawhide patches.
Dave Jones ([EMAIL PROTECTED]) said: linux-2.6-defaults-fat-utf8.patch Drop? Isn't this a local choice similar to the later ones? linux-2.6-net-silence-noisy-printks.patch linux-2.6-piix3-silence-quirk.patch linux-2.6-quiet-iommu.patch linux-2.6-silence-acpi-blacklist.patch linux-2.6-silence-fbcon-logo.patch linux-2.6-silence-noise.patch Fedora local 'hush' patches. Speaking of 'hush' patches - ... ALSA sound/pci/hda/hda_intel.c:1404: azx_pcm_prepare: bufsize=0x1, format=0x4011 ALSA sound/pci/hda/hda_codec.c:716: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x4011 ... Is this a config option, or do we need to patch this stuff out? Bill ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: rawhide patches.
On Thu, Sep 25, 2008 at 03:07:04PM -0400, Bill Nottingham wrote: Dave Jones ([EMAIL PROTECTED]) said: linux-2.6-defaults-fat-utf8.patch Drop? Isn't this a local choice similar to the later ones? The problem is this is a who do we want to screw over patch. Some people have disks which aren't UTF8, and get crazy moon language instead of their expected charset. linux-2.6-net-silence-noisy-printks.patch linux-2.6-piix3-silence-quirk.patch linux-2.6-quiet-iommu.patch linux-2.6-silence-acpi-blacklist.patch linux-2.6-silence-fbcon-logo.patch linux-2.6-silence-noise.patch Fedora local 'hush' patches. Speaking of 'hush' patches - .. ALSA sound/pci/hda/hda_intel.c:1404: azx_pcm_prepare: bufsize=0x1, format=0x4011 ALSA sound/pci/hda/hda_codec.c:716: hda_codec_setup_stream: NID=0x2, stream=0x5, channel=0, format=0x4011 .. Is this a config option, or do we need to patch this stuff out? Probably one of the many ALSA debug options. CONFIG_SND_VERBOSE_PRINTK=y CONFIG_SND_DEBUG=y CONFIG_SND_DEBUG_DETECT=y CONFIG_SND_DEBUG_VERBOSE=y CONFIG_SND_PCM_XRUN_DEBUG=y Dave -- http://www.codemonkey.org.uk ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: de-modularising for the win!
On Thu, 2008-09-18 at 12:13 -0700, Bill Nottingham wrote: See various and sundry plumber's conf discussions. Comments? (The netfilter stuff needs further investigation.) I'm ok with all of these specific config changes, but I'd like to repeat what I said in Kyle's session about demodularising in general. I advocate extreme caution before just willy-nilly building everything into the kernel. Although this might seem like a great idea from the point of view of speeding up boot, there is also the pesky issue of users wanting the choice to decide which modules get loaded, and more importantly, wanting to override those modules with their own. To do this truly right we'll need to do rebinding of drivers in kernel. That's not always going to be easily possible after it's in use. And while we might not love binary drivers, note that it is the user's choice to make. If they want to load proprietary (or just out of tree drivers) then we should not go out of our way to intentionally make this difficult for them. i.e. let's no go building in particular graphics drivers for political reasons...I'm pre-empting discussion there :) So, anyway, Bill's got a good base set of common options. Jon. ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: chcorefilter
On Thu, Sep 25, 2008 at 05:32:50PM -0700, Roland McGrath wrote: Content-Description: message body text The /proc/PID/coredump_filter mechanism makes it easy to tweak the per-process setting to control ELF core dump style details. This setting is per-process (per-mm) and inherited by children. But as a user, the /proc interface is insane. It prints a magical hex value (without a leading 0x, to make it sneaky), which you'll be damn lucky to figure out from reading Documentation/filesystems/proc.txt. Then you get to set it to another such magical value, which is in decimal unless you add a leading 0x (cat /proc/x/coredump_filter /proc/y/coredump_filter does not copy the setting, go team). I have kicking around this half-assed bash script that I don't care to bother making really presentable. Where should it live? In the upstream kernel's scripts/? (Then noone would ever see it for sure.) In util-linux-ng? Or what? Someone want to take it off my hands? either util-linux or procps is my suggestion. Dave -- http://www.codemonkey.org.uk ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
