mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Greg Stark <gsstark@MIT.EDU>
Cc: gsstark@MIT.EDU, s0348365@sms.ed.ac.uk,
	linux-kernel@vger.kernel.org, pmcfarland@downeast.net
Subject: Re: OSS Audio borked between 2.6.6 and 2.6.10
Date: Sun, 13 Mar 2005 21:57:10 -0800	[thread overview]
Message-ID: <20050313215710.5fa920d4.akpm@osdl.org> (raw)
In-Reply-To: <87zmx66b2b.fsf@stark.xeocode.com>

Greg Stark <gsstark@MIT.EDU> wrote:
>
>  Greg Stark <gsstark@MIT.EDU> writes:
> 
>  > Andrew Morton <akpm@osdl.org> writes:
>  > 
>  > > Are you able to narrow it down to something more fine grained than "between
>  > > 2.6.6 and 2.6.9-rc1"?
>  > 
>  > Er, I suppose I would have to build some more kernels. Ugh. Is there a good
>  > place to start or do I have to just do a binary search?
> 
>  Oof. I just skimmed the Changelogs. It looks like the i810 OSS drivers got
>  quite a rototilling in 2.6.7 and 2.6.8. It also kind of sounds like they
>  needed it though.

The 2.6.6 i810_audio.c compiles OK in current kernels with the below patch
applied.  

--- 25/sound/oss/i810_audio.c~a	2005-03-13 21:54:00.000000000 -0800
+++ 25-akpm/sound/oss/i810_audio.c	2005-03-13 21:56:29.000000000 -0800
@@ -1758,7 +1758,8 @@ static int i810_mmap(struct file *file, 
 	if (size > (PAGE_SIZE << dmabuf->buforder))
 		goto out;
 	ret = -EAGAIN;
-	if (remap_page_range(vma, vma->vm_start, virt_to_phys(dmabuf->rawbuf),
+	if (remap_pfn_range(vma, vma->vm_start,
+				virt_to_phys(dmabuf->rawbuf) >> PAGE_SHIFT,
 			     size, vma->vm_page_prot))
 		goto out;
 	dmabuf->mapped = 1;
@@ -3349,7 +3350,7 @@ static int i810_pm_suspend(struct pci_de
 			}
 		}
 	}
-	pci_save_state(dev,card->pm_save_state); /* XXX do we need this? */
+	pci_save_state(dev); /* XXX do we need this? */
 	pci_disable_device(dev); /* disable busmastering */
 	pci_set_power_state(dev,3); /* Zzz. */
 
@@ -3362,7 +3363,7 @@ static int i810_pm_resume(struct pci_dev
 	int num_ac97,i=0;
 	struct i810_card *card=pci_get_drvdata(dev);
 	pci_enable_device(dev);
-	pci_restore_state (dev,card->pm_save_state);
+	pci_restore_state (dev);
 
 	/* observation of a toshiba portege 3440ct suggests that the 
 	   hardware has to be more or less completely reinitialized from
_


  reply	other threads:[~2005-03-14  5:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 18:31 Greg Stark
2005-03-13  6:52 ` Patrick McFarland
2005-03-13 22:26   ` Greg Stark
2005-03-14  0:48     ` Martin Schlemmer
2005-03-14  1:03     ` Alistair John Strachan
2005-03-14  3:50       ` Greg Stark
2005-03-14  4:07         ` Andrew Morton
2005-03-14  4:42           ` Greg Stark
2005-03-14  4:55             ` Andrew Morton
2005-03-14  5:39             ` Greg Stark
2005-03-14  5:57               ` Andrew Morton [this message]
2005-03-14  6:21                 ` Greg Stark
2005-03-14  6:48                   ` Andrew Morton
2005-03-14  8:59               ` Greg Stark
2005-03-14  9:53                 ` Andrew Morton
2005-03-14 15:40                   ` Greg Stark
2005-03-14 15:52                     ` John W. Linville
2005-03-22  0:38                     ` Andrew Morton
2005-03-22  4:16                       ` Greg Stark
2005-03-14 15:33                 ` John W. Linville

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050313215710.5fa920d4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gsstark@MIT.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmcfarland@downeast.net \
    --cc=s0348365@sms.ed.ac.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome