Hi Mike,
The software I am using in Linux (cajun - cajun.sourceforge.net)
requires
a serial display to work. What the linux driver does is emulate the
serial
display, and provides a /dev/lcd.
As I am not a perl coder, I cannot modify Cajun to use the app you
wrote,
And as I am not a C coder, I c
It seems Alex Zepeda wrote:
> On Mon, Apr 30, 2001 at 12:08:47AM +0200, Torbjorn Kristoffersen wrote:
>
> > Yes, I'm using the 80-conductor cable I got with the motherboard
> > (ABIT BE6 with HPT366 onboard).
>
> Is the cable connected properly? The blue connector must be on the
> motherboard e
On Mon, Apr 30, 2001 at 12:08:47AM +0200, Torbjorn Kristoffersen wrote:
> Yes, I'm using the 80-conductor cable I got with the motherboard
> (ABIT BE6 with HPT366 onboard).
Is the cable connected properly? The blue connector must be on the
motherboard end.. Are you sure Leenuchs is using ATA66
On Mon, 30 Apr 2001, Søren Schmidt wrote:
> It seems Torbjorn Kristoffersen wrote:
> > On Sun, 29 Apr 2001, Mike Silbersack wrote:
> > > On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote:
> > > > I'm having trouble with my HighPoint 366 controller. Both the chip and
> > > > cable works fine in L
It seems Torbjorn Kristoffersen wrote:
> On Sun, 29 Apr 2001, Mike Silbersack wrote:
> > On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote:
> > > I'm having trouble with my HighPoint 366 controller. Both the chip and
> > > cable works fine in Linux or Windows, but I get an error message from
> > >
On Sun, 29 Apr 2001, Mike Silbersack wrote:
>
> On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote:
>
> > I'm having trouble with my HighPoint 366 controller. Both the chip and
> > cable works fine in Linux or Windows, but I get an error message from
> > FreeBSD 4.3-RC2 that says "DMA limited to U
> Hi Patrick,
>
>
> I didn't really explain much about the LCD+Driver...
> Basically its a parallel port display that uses the generic Hitachi
> HD44780
> chipset. What the driver for linux does is provide a /dev/lcd
> that you can address the same as you would /dev/cuaaX for a serial
> matrix o
Hi,
On Sat, Apr 14, 2001 at 02:48:36PM +0200, Martin Blapp wrote:
> Can you check if this solves the drac problem in CURRENT ?
> Does drac work the way it should ? There were some flags
> actived in rpcgen, which shouldn't have been. I also modified
> your port a bit to use tirpc code and to not
On Sun, 29 Apr 2001, Torbjorn Kristoffersen wrote:
> I'm having trouble with my HighPoint 366 controller. Both the chip and
> cable works fine in Linux or Windows, but I get an error message from
> FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 compliant
> cable."
Well, are you usi
I'm having trouble with my HighPoint 366 controller. Both the chip and
cable works fine in Linux or Windows, but I get an error message from
FreeBSD 4.3-RC2 that says "DMA limited to UDMA33, Non-ATA66 compliant
cable."
Here is my dmesg output with a kernel verbosely booted. I have carefully
erase
In message <[EMAIL PROTECTED]> Peter Seebach writes:
: In message <[EMAIL PROTECTED]>, Jos Backus writes:
: >Yeah, I am just puzzled as to how this can build at all on other platforms
: >(Linux?), unless they don't define this variable.
:
: Many of them probably have it as an external object, not
In message <[EMAIL PROTECTED]>, Jos Backus writes:
>Yeah, I am just puzzled as to how this can build at all on other platforms
>(Linux?), unless they don't define this variable.
Many of them probably have it as an external object, not a #define. I'm
still not sure the code makes any sense.
-s
Hi Patrick,
I didn't really explain much about the LCD+Driver...
Basically its a parallel port display that uses the generic Hitachi
HD44780
chipset. What the driver for linux does is provide a /dev/lcd
that you can address the same as you would /dev/cuaaX for a serial
matrix orbital display.
T
13 matches
Mail list logo
