Date: Mon, 16 Oct 2006 08:40:04 +0200 From: usleepless@gmail.com To: rick-freebsd@kiwi-computer.com Cc: freebsd-multimedia@freebsd.org, B Briggs <rcbdyndns@bellsouth.net> Subject: Re: New port: pvrxxx for Hauppauge PVR150/500 Message-ID: <c39ec84c0610152340u2af2aeco611086e50f467a6a@mail.gmail.com> In-Reply-To: <20061016015911.GC57865@keira.kiwi-computer.com> References: <45317970.5000508@bellsouth.net> <20061015064102.8780.qmail@web30310.mail.mud.yahoo.com> <20061016015911.GC57865@keira.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi All, On 10/16/06, Rick C. Petty <rick-freebsd@kiwi-computer.com> wrote: > > You might be right that there's no EEPROM/Flash. But the DSP chip(s) > is/are programmed through the I2C bus, at least that's what usleep hinted. correct. however, ivtv seems to be able to download it much faster. i have experimented with speeding up the i2c stuff, but failed ( ie gave up ). > > Maybe it is possible to continue with other things, when locking is done > less > > strict? Or does firmware upload require some important bus (like PCI) > during > > the whole time? > > I think it's timing-critical, although an I2C bus has clock and data lines, > so I can't see any reason the kernel needs to block during the download. > Feel free (anyone) to look into the iic code and pull it out from under > GIANT. will that help? reason i ask is because with the i2c, the cpu is responsible for every bit-switch/line-switch in the protocol. so through the pci-interface, it tells the card to pull the line up, you wait a very short time, and tell it to pull the i2c-line down. etc... this weekend, i removed Giant from the pvrxxx-driver itself. i am on UP myself, so i don't know what it is good for. regards, usleep
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c39ec84c0610152340u2af2aeco611086e50f467a6a>